-
-
Notifications
You must be signed in to change notification settings - Fork 345
Commit
…ity on the web unfortunately, too many sites check for browser name instead of feature detection. Pretend we're 57.0 as well, so add-ons install propely on the Mozilla AMO.
- Loading branch information
There are no files selected for viewing
6 comments
on commit 3391281
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pretend we're 57.0 as well, so add-ons install propely on the Mozilla AMO.
Hi @MrAlex94 , this change actually hoses AMO for Waterfox users. It causes AMO to block installation of compatible legacy extensions (like Classic Theme Restorer) and allow installation of some incompatible WebExtensions (like NoScript 10.1.6.5).
I understand if having the full Waterfox UA is sadly not practical, but could you please revert the version number change?
Thanks
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I see, seems I've made a couple of mistakes with this patch (especially the compatibility version - need to update that). Will see the best course of action tomorrow :-). Thanks for the heads up!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@laniakea64, setting extensions.checkCompatibility.56.1;false
in about:config fixes all the issues. Give it a try? Managed to install both NoScript and CTR.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It doesn't seem to have any effect here. AMO still blocks installation of CTR and allows installation of NoScript 10.1.6.5.
Perhaps I wasn't quite clear about what the problem is. Waterfox itself behaves correctly: installing CTR from a downloaded .xpi works fine, and Waterfox correctly rejects the incompatible NoScript 10.1.6.5. The problem here is how AMO behaves in response to detecting version 57 from the UA.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@MrAlex94 @laniakea64 over to #484 (if you don't mind; an issue might be easier to track if I'm to rope in help from elsewhere).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes sorry, seems I stupidly was testing installing CTR in the current release of Waterfox, got the windows confused 😂. Fixed the issues of not installing WebExtensions though.
I'm not sure what to do here, I'll see if it's worth implementing the archive store and using that for the older add-ons 🤔 as a replacement to the add-ons manager?
nit: there shouldn't be a space between
rv:
and the version number