RIP firefox

RIP firefox

For the time being, I'm going to stop building the webext version of uBO, there are too many serious issues now with it. I will resume when things stabilize, it's unclear whether it is expected things will have to change in uBO or whether things will be fixed in webext.

About accessing the dashboard, it's unclear to me whether this is something that will be fixed in WebExtensions[1], the answer from the Firefox dev is ambiguous: bugzilla.mozilla.org/show_bug.c ... 368152#c15. (I am being told the URL is not valid, then that it's not supported, then pointed to a bug issue where it's unclear whether it will fix the particular issue affecting uBO).

I could create a link to the dashboard, but this would mean downgrading uBO's current behavior: currently, if the dashboard is already opened, uBO will merely just activate the tab. If I have to change this to a plain link, then this means the tab will be reloaded, and any changes not yet committed in the dashboard would be lost. But anyways, this would not solve the document-blocked case, where uBO really need to programmatically load the tab with a specific moz-extensions: URL.

The performance issue is real, I did run some benchmarks a while ago using the page-load-speed tool, and there is definitely an extra overhead incurred with WebExtensions. The webext version of uBO is pretty much exactly the Chromium version of uBO (code is imported as is), and it performs excellently on Chromium. Wherever uBO performs best, I consider this the reference performance, and if one platform suffers performance regression, this has to be addressed by the platform.

I've put (and still do) a lot of work into finding out where things can be improved, and it's discomfiting to see these performance gains being negated on the current webext platform. Hopefully with the ongoing work being done on the webext API, these issues will resolve with time.
- gorhill

forums.mozillazine.org/viewtopic.php?p=14751077#p14751077

>im just here to block your ads

Pale Moon doesn't have this problem.

Firefox really is a mess
is Nightly any better ?

Read the fucking thread, you meme spouting nigger, this is an issue concerning Nightly and that won't affect stable Firefox until November, provided it isn't fixed by then.

It's temporarily frozen because they have to fix bugs. Also, it's only for the beta version. Why are you trying to make a big deal out of it?

i don't care about your fucking issue, firefox is such an unresponsive cpu fucking memory eating piece of retarded nigger shit nowadays and i asked if nightly builds are any better

Well there is no better alternative so I can wait

>RIP firefox
he's just putting pressure on the devs. there's still half a year left before webex support needs to be ready. and if it isn't they can still push it back to the next release

is that a woman