Fix updating and support of legacy javascript extensions.
Update to 2.53.7
Enable support for module scripts. (To turn it off, toggle "dom.moduleScripts.enabled" in about:config).
For sending mail, now "Thunderbird" is advertised in User-Agent header instead of "Firefox" (if any).
Some performance fixes, including from upcoming releases.
Updates may require up to 24 hours to propagate to mirrors. If the following command doesn't work, please retry later:
sudo dnf upgrade --refresh --advisory=FEDORA-2021-2761b54dff
Please login to add feedback.
This update has been submitted for testing by buc.
This update's test gating status has been changed to 'ignored'.
This update's test gating status has been changed to 'waiting'.
This update has obsoleted seamonkey-2.53.7-1.fc33, and has inherited its bugs and notes.
This update's test gating status has been changed to 'ignored'.
seems to work nice, thx buc!
This update has been pushed to testing.
Works for me.
This update can be pushed to stable now if the maintainer wishes
This update has been submitted for stable by bodhi.
This update has been pushed to stable.
Broke tab switching with mouse wheel for me, I raised https://bugzilla.mozilla.org/show_bug.cgi?id=1704151 upstream.
@lam, it looks like upstream bug 1702903 (will be fixed in upcoming release soon).
To fast check without recompiling, you can try to apply changes from https://bugzilla.mozilla.org/show_bug.cgi?id=1702903#c4 against omni.ja:modules/commonjs/sdk/ (it is zip archive actually).
@buc, yes, that did the trick!
After patching the files inside, I zip -0'd everything back in to keep it "as intended" (apparently it was more of a tar in zip form), and you were right, that totally fixes my extension problem!
I'm now a happy 2.53.7 user and will go report back in moz-bz.
Thanks a lot! I would never find that bug by my symptoms!
[I even tried rebuilding without seamonkey-2.53.7-refresh.patch before, seeing that it did have something to do with "scrolling" (yes, I know, not that kind of scrolling, but what do I know about event propagation in SM), that wasn't it obviously, but it made me more confident to report it upstream.]