New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Latest Stylus 1.5.38 no longer handles styles for addons.mozilla.org #1701
Comments
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
I've tested the old version, sorry. I see the bug. The workaround is to enable Preliminary investigation indicates the old Stylus miraculously exploited a bug in Firefox and managed to ignore CSP, so if this is indeed so, we won't re-enable the exploit... |
OK. Thanks for your quick response. EDIT : |
Amazing how even a tiny issue at start can end up to true discoveries after investigation :) |
I've decided to restore the exploit in db119ba because it matches the intentional behavior in Chrome and Mozilla doesn't want to fix it: https://bugzil.la/1706787. Regardng adoptedStyleSheets, it's a new thing and it may be bugged in some cases e.g. theoretically the styles may be removed or re-ordered by another script and we won't detect it due to the lack of an efficient observation/notification method in this API. |
I've been seeing this problem in other sites too (e.g. https://pypi.org on Firefox). Has it been considered to enable the Circumvent CSP 'style-src' via adoptedStyleSheets setting by default? My 50 cents: It seems to me many are going to be hitting this issue, and the solution may not be so obvious for non-web developers. |
I guess we can enable it as an automatic fallback in case the CSP blocked the style and show a corresponding warning in the popup... |
+ auto-switch to adoptedStyleSheets if failed
@Mottie, how about posting a beta in CWS and then release everywhere at the end of the week? Looks like I've just found a way to circumvent CSP entirely in Firefox, which has been bugging more and more users recently as the sites tighten up. |
Enable |
The new 1.5.39 should have fixed it, which is why the issue is closed. If you can't use it as a temporary extension, try using the previous working version 1.5.35. The new version will be released in a week, hopefully. |
Previous 1.5.35 has always ran flawlessly. Problem with running older versions than current is that extensions' updates will overdo them if automatic and otherwise forces the user to be aware when updating manually as I do. I run 60+ extensions and several happen to be "updatable" simultaneously. |
I'm not offended, I understand the pain. Unfortunately such bugs are inevitable as no one regularly tests the extension in Firefox since Mozilla removed the support for beta versions from AMO. |
v1.5.39 submitted to CWS & AMO |
Wait, there are some trivial fixes since then, so maybe cancel the one on AMO and upload 1.5.40? I'm not sure you can cancel a pending update on CWS though, previously it was impossible, IIRC. @Mottie |
I can't remember either... let's wait until tomorrow |
And may not handle as well styles for other "reserved" domains (haven't tested widely).
Environment : Stylus 1.5.38 / Firefox 115.5.0 ESR / Windows 7
Of course
toolkit.legacyUserProfileCustomizations.stylesheets
has always been set to true in about:config.No issues with Stylus 1.5.35 from which I've updated to 1.5.38
At this point I have to remove from my Stylus styles the style pertinent to addons.mozilla.org and add it to my userContent.css file, where it works fine.
Any clue?
The text was updated successfully, but these errors were encountered: