mancode20 wrote:Will Stylish be fixed in Nightly? I hope so!
Current dev builds on Github are already fixed: https://github.com/JasonBarnabe/stylish
-> "Download Zip"
-> unpack
-> open "stylish-master" folder
-> zip content of that folder
-> move zip file into add-ons manager to install the new version
JayhawksRock wrote:maybe 2 downloaders are trying to use the same native function at the same time ? Disable one, restart Fx and see what happens
Thank you for the suggestion, but I had each in a separate profile. They were, as far as I understand things, never actually in a position to "conflict" with each other.
Although every day is Judgment Day, I nonetheless feel like a room without a roof.
mancode20 wrote:Will Stylish be fixed in Nightly? I hope so!
Current dev builds on Github are already fixed: https://github.com/JasonBarnabe/stylish
-> "Download Zip"
-> unpack
-> open "stylish-master" folder
-> zip content of that folder
-> move zip file into add-ons manager to install the new version
Through your link I was able to find an easier solution. I just had to download and install the newest Stylish 2.0.5b1 from this link. https://forum.userstyles.org/discussion/48357 Make sure xpinstall.signatures.required is set to false in about:config to make sure you can install it. So nice to have Stylish back again! Thanks!
As mentioned Stylish with the patch above is partially broken. When I click on 'Write New Style' or try to Edit one nothing happens. However, in about:support the 'Multiprocess Windows' entry count goes up every time you click on the stylish buttons I just mentioned. Normally when you exit the Stylish edit window the task is terminated however with the patch it never does so the count remains the same. When you exit Fx the Nightly bg task shows up in Task Manager.
I contacted Jason B about the patch but haven't got a reply back yet.
Indeed. I only had 2 that didn't work out of 24 add-ons so perhaps it's not that widespread. Of course if it stops a must have add-on from working then it's a big deal no matter if it's wide spread or not.
Intel i9-13900K | ASUS ROG MAXIMUS Z790 HERO DDR5 | 64GB CORSAIR VENGEANCE DDR5 @ 6600 Mhz.
H100i ELITE CAPELLIX XT Liquid CPU Cooler | PNY 12GB GeForce RTX 3080 Ti | 2 CORSAIR 2TB MP600 PRO XT GEN 4
HX1200 PLATINUM PSU | XENEON 32" IPS UHD 144Hz | BenQ 32" UHD | MS Windows 11 Pro
I got pinged that my addon was broken because of this. It has a "for each" but I don't recall ever seeing any console warnings about it being deprecated. Turns out it was only deprecated in Firefox 51, hardly seems worth the effort.
lithopsian wrote: Turns out it was only deprecated in Firefox 51, hardly seems worth the effort.
You mean fixing it? You'd rather have it broken?
No, it hardly seems worth the effort of deprecating something, updating the documentation and adding console warnings, none of which I saw because they didn't even hit release before they were completely deleted from nightly as a fairly brutal experiment to see who was still using it.
for (let property in aButtons)
{
let button = buttons[property];
...
Slightly more clunky but equivalent and robust.
Depending on the exact situation, you may be able to just replace the for each ... in with for ... of. The for ... of construct also iterates over the values of the properties of aButtons, but it only works for certain types of object so you can't always just drop it in.
mozillaZine is an independent Mozilla community and advocacy site. We're not affiliated or endorsed by the Mozilla Corporation but we love them just the same.