Skip to content
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

DownThemAll no longer functions under Nightly 136.0a1 starting 2025-01-23-21-50-52 #336

Open
jiangzhenjerry opened this issue Jan 24, 2025 · 8 comments

Comments

@jiangzhenjerry
Copy link

As the title suggested, Firefox once again (!) breaks DownThemAll. DTA does not show in Context menu or Dropdown menu.

Problematic build: https://ftp.mozilla.org/pub/firefox/nightly/2025/01/2025-01-23-21-50-52-mozilla-central/firefox-136.0a1.en-US.win64.installer.exe
Last working build: https://ftp.mozilla.org/pub/firefox/nightly/2025/01/2025-01-23-09-52-38-mozilla-central/firefox-136.0a1.en-US.win64.installer.exe

@117649
Copy link

117649 commented Jan 24, 2025

See #333 #335

@Zhiro90
Copy link

Zhiro90 commented Feb 2, 2025

FF Nightly 136a With the fixes mentioned in the thread, got these scripts working as of feb 3:

Supposed to work:

  • Tabmixplus: Has been updated, haven't updated it yet
  • Styloaix: It's mentioned in the linked issues that it's partially working, haven't tinkered with it again yet

These scripts are still broken:

  • Mouse Gestures
  • Enter Selects
  • Private Tab

if a script isn't listed here is because I don't use it.

On the other hand All legacy extensions that I use (save file to, rehost image, pilfer, norwell history, downthemall, dorando keyconfig and backtrack tab history) have been disabled with no option to enable, about:config option to ignore signatures is greyed out, would need to wait for extensions updates

@marty60
Copy link

marty60 commented Feb 5, 2025

On the other hand All legacy extensions that I use (save file to, rehost image, pilfer, norwell history, downthemall, dorando keyconfig and backtrack tab history) have been disabled with no option to enable, about:config option to ignore signatures is greyed out, would need to wait for extensions updates

Fixing keyconfig was pretty straightforward but when trying to reinstall it I'm getting "the addon appears corrupt" message so I don't know what the problem is. Fortunately benzBrake's keyconfig script still works great provided "security.browser_xhtml_csp.enabled" is toggled false.

https://github.com/benzBrake/FirefoxCustomize/tree/master/userChromeJS/KeyChanger

There are event handlers that need to be updated in some of these scripts and setting security.browser_xhtml_csp.enabled to true will break them.

Dumby's custom buttons paxmod version still works too thankfully so all is not completely lost yet...

@Zhiro90
Copy link

Zhiro90 commented Feb 5, 2025

when trying to reinstall it I'm getting "the addon appears corrupt" message so I don't know what the problem is.

looking around it seems to be related to signatures. Adding a manifest xml and submitting to firefox extensions website as a personal use extension supposedly works but when i tried that for savefile to, although it did let met install it, it wasn't functioning.

@kaos-55
Copy link

kaos-55 commented Feb 5, 2025

Fortunately benzBrake's keyconfig script still works great provided "security.browser_xhtml_csp.enabled" is toggled false.

This is a temporary fix, and Firefox plans to remove this option in the future.

There are event handlers that need to be updated in some of these scripts and setting security.browser_xhtml_csp.enabled to true will break them.

Unfortunately, several if not all of the scripts need to be refactored to work with Firefox 136, and given the lack of interest in updating the scripts by the owner of this repository, I think this is the end for these scripts unless someone takes over and updates them, which I highly doubt anyone will want to do.

@marty60
Copy link

marty60 commented Feb 5, 2025

when trying to reinstall it I'm getting "the addon appears corrupt" message so I don't know what the problem is.

looking around it seems to be related to signatures. Adding a manifest xml and submitting to firefox extensions website as a personal use extension supposedly works but when i tried that for savefile to, although it did let met install it, it wasn't functioning.

That's interesting, I'll have to upload the addons that I've updated to my extensions account and see if that will get them to install.

Another option is to do what Dumby does with his legacy custom buttons addon. He provides two versions: a bootstrap.xpi and paxmod.xpi. The paxmod one uses the experiment_script and seems to bypass some of the problems.that keep popping up with the constant code changes.

@marty60
Copy link

marty60 commented Feb 5, 2025

Unfortunately, several if not all of the scripts need to be refactored to work with Firefox 136, and given the lack of interest in updating the scripts by the owner of this repository, I think this is the end for these scripts unless someone takes over and updates them, which I highly doubt anyone will want to do.

Well good news for keyconfig users: benzBrake updated the KeyChanger.uc.js today so now I'm able to toggle "security.browser_xhtml_csp.enabled" back to true and all of my custom buttons and scripts work. Now it's just getting the extensions back online.

Thanks to @117649 for updating the rebuild_userChrome.uc.js file:

rebuild_userChrome.uc.js.zip

@Zhiro90
Copy link

Zhiro90 commented Feb 6, 2025

That's interesting, I'll have to upload the addons that I've updated to my extensions account and see if that will get them to install.

be sure to share any that you manage to get working again

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants