Not wanting to wreck my regular profile, I tested in Firefox Developer Edition, which is based on the beta of Firefox 94.
I can't replicate the data loss with either:
mature
key retained)I don't know whether that is due to changes in Firefox 94 or a configuration difference.
Firefox 57 will no longer run "Legacy" extensions, only ones that use the WebExtensions API. I don't know whether there is a switch to allow Legacy extensions (there may be an earlier thread on this). If not, you could switch to the Developer Edition, which I think is a variant of Firefox Beta. https://www.mozilla.org/firefox/developer/
Other replies point out that some Legacy extensions still work in Nightly 57.
When Stylish is finally history:
For website styles you can use the Stylus extension or others that may come along.
For browser styles, you can use a userChrome.css file.
Ok... it seems like DevEdition is what you need https://www.mozilla.org/firefox/developer/
It's not a shame that Stable does not accept unsigned extensions. I'm glad it's impossible for my mom to install some evil addons on her computer.
Create a new profile in about:profiles
and install only uBlock Origin. See how that works.
If you are eager to see the new stuff faster, DevEdition is a good balance between new and stable.
December 7th. You could test Developer Edition now: https://www.mozilla.org/firefox/developer/
You also could consider switching the new tab button / Ctrl+t to opening the tab immediately adjacent to the current tab if that is your usual scenario for using the context menu:
(1) In a new tab, type or paste about:config in the address bar and press Enter/Return. Click the button accepting the risk.
(2) In the search box in the page, type or paste insert and pause while the list is filtered
(3) Double-click the browser.tabs.insertAfterCurrent preference to switch the value from false to true
I am not one of the developers, no.
I wonder whether it is worth filing a bug against Firefox saying PDF X works in the development edition but not in Firefox 82. When do we expect it to work in Firefox? Just in case it's a theme issue.
You also could take a look in Firefox Developer Edition (future Firefox 83). It can install side-by-side with the regular release. https://www.mozilla.org/firefox/developer/
It is easiest two use two different browsers for your use case. You can use standard Firefox for one profile (work or home) and Firefox Developer Edition for the other.
This makes it easy to have both logged in and syncing at once.
Chromium is still developed by Google and helps Google controlling the web. Also, you should add feature requests for DevTools features that you would like to see in Firefox here. Also, you might want to check Firefox Developer Edition which has better developer tools than normal editions. Some things are better than in Chrome, and some are not.
You could install Firefox Developer Edition on the side and test the level of breakage of your userChrome.css that way. (You'll need to flip the preference to look for the file at startup because Developer Edition will use a new profile.)
https://www.mozilla.org/firefox/developer/
That's probably more practical than trying to sift through hundreds of potentially irrelevant changes.
There's something, (I don't know if it's built in or some other plugin) in the Firefox Developer Edition that shows you what elements have an event handler assigned to it, and links you to the relevant source code. That could be helpful, assuming it's in some event handler related to the element that adds it.
That said, it doesn't handle callback-spaghetti and event bubbling perfectly, so your mileage may vary.