However, it appears that this native useful feature was again binned, starting with Firefox Browser (previously known as "Quantum") v71.0 (currently in the beta channel) this time, the original SSUAO supporting module (UserAgentOverrides.jsm) was completely excised, reason being "it was just old code", and those users wanting the removed functionality back should, once again, resort in using a dedicated (WE) addon. The feature supporting module (UserAgentOverrides.jsm) was still kept in the source tree, but was not initialised in desktop Fx versions - hence the need of an extension (or additional code) to re-initialise it properly in Fx ESR 52.9.x :angry: I was alerted by the following Mozillazine thread:īugzilla bug #1513574 : Remove UserAgentOverrides.jsmĭuring the pre-Australis era, Mozilla had implemented native SSUAO support in Firefox, but then disabled it at some point (in Fx 25.0 ?) in desktop Firefox (but kept it in the mobile version) to, supposedly, gain a 7% speed increase in page loading times. However, it appears that this native useful feature was again binned, starting with Firefox Browser (previously known as " Quantum") v 71.0 (currently in the beta channel) this time, the original SSUAO supporting module ( UserAgentOverrides.jsm) was completely excised, reason being " it was just old code", and those users wanting the removed functionality back should, once again, resort in using a dedicated (WE) addon. In a previous MSFN post, I had searched Bugzilla and found that the SSUAO native feature was again restored in Fx 55.0, so from Fx 55.0+ one would not need extensions (legacy/WE) or JS code to apply SSUAOs in the browser. The feature supporting module ( UserAgentOverrides.jsm) was still kept in the source tree, but was not initialised in desktop Fx versions - hence the need of an extension (or additional code) to re-initialise it properly in Fx ESR 52.9.x It's funny you mentioned SSUAO in Firefox, because today I became aware of another Mozilla change involving SSUAO support in Firefox.ĭuring the pre-Australis era, Mozilla had implemented native SSUAO support in Firefox (but I'm now too lazy to search and quote relevant Bugzilla bugs, it's 01:50 AM on Friday already here.), but then disabled it at some point (in Fx 25.0 ?) in desktop Firefox (but kept it in the mobile version) to, supposedly, gain a 7% speed increase in page loading times. Luckily, hiding warnings (with, e.g., the Classic Theme Restorer add-on) will hide these scarier messages just as it hides the yellow warnings in FF 52 ESR. However, it has not been disabled you'll still see a "disable" button which wouldn't be there if the add-on were already disabled. Instead, you'll see a scarier, red "This has been disabled" message. Since FF 53 doesn't expect to have add-on signing disabled, it doesn't have the yellow "warning" text that FF 52 ESR does for an "unverified" add-on. (I put it after code, but it will probably work before it too.) The workaround at the link can be combined with fix for re-enabling SSUAOs in Firefox 52:įirst, follow the instructions there then add this JavaScript to the config.js file you just created: Luckily, there is a workaround, but it's a bit more complex than just setting a preference. You can even hide the warnings with an add-on like Classic Theme Restorer.īut FF 53 is a "stable" release, and doesn't work in stable FF releases. The unsigned add-ons will produce warnings in the about:addons page, but they work. You simply set the about:config preference to false and you're good to go. In FF 52 ESR, unsigned add-ons aren't much of a problem. (A couple were add-ons that were originally signed, but from which I had removed the signature in order to implement some hack.) The biggest example was the legacy version of uBlock Origin, which I use because it offers more privacy protections than the WebEx version does on FF 52 and 53. Usually these were legacy add-ons that continued to be maintained after Mozilla banned pre-WebEx add-ons, and thus could no longer get Mozilla to sign them. When I tried out FF 53, I discovered that some of my add-ons got disabled.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |