Misbehaving on Firefox

[Ian-Naxieas]

Hello!

I've been using this script for several months, but it's recently started acting up.

• Firefox Add-On Broken #13

I have been having this same issue, but I've been unable to fix it. First, I made sure Firefox wasn't set to strict.

I've tried deleting and reinstalling the script, switching from Tampermonkey to Violentmonkey, and installing the script fresh. I've disabled all other extensions and scripts. Nothing I've tried has fixed the issue permanently, though I have made a few observations.

I could get it working again on Tampermonkey if I turned the script off, refreshed, turned it back on, and refreshed again. It would work as long as I stayed on that page, but it would break again if I went to a different page.

As for Violentmonkey, just refreshing would very rarely fix it for that page, but if I use Ctrl+F5, it always fixes it for that page, but breaks again when I go to a different one.

Ultimately, hitting Ctrl+F5 on a page with media is no big deal, but naturally, I'd rather have it fixed. x) Regardless, thank you for your time!

[AlttiRi]

I can reproduce.

---

Currently, you can use:

But it disables the download progress bar.

---

I need just to use GM_fetch, instead of the native fetch. It's less optimal, but it will work without problems on FF.

---

The Permission denied to access property "autoAllocateChunkSize" Firefox' bug is damning annoying.

[Ian-Naxieas]

Currently, you can use:

But it disables the download progress bar.

Sure enough, that did the trick. I've been doing my best to break it, but it's been working perfectly, and I can live without the progress bar. That was the only step I didn't try; I figured it was pointless, as I wasn't running in strict mode. Sorry for that, but thank you for your time and hard work!

[AlttiRi]

You can replace this line

twitter-click-and-save/twitter-click-and-save.user.js

Line 2483 in c73bbd1

const readableStream = new ReadableStream({

with

const readableStream = new unsafeWindow.ReadableStream({

The download progress will work again with "Enhanced Tracking Protection" in "Standard" mode.

UPD: But only in VM, not TM.

---

However, it seems, that it makes sense to not create ReadableStream at all.
Only create a new ResponceEx from Blob from reader.read() chunks.
In this case the download progress will work even with "Enhanced Tracking Protection" in "Strict" mode (with some workaround).
I will do it later.

[AlttiRi]

Should be fixed in bf82eb2 (1.16.0-2025.06.26).

You can try it with GitHub version for now:
https://github.com/AlttiRi/twitter-click-and-save/raw/refs/heads/master/twitter-click-and-save.user.js

UPD: Released on Greasyfork.

[AlttiRi]

Also, it shows the download size in the button's title now:

f3e9fa0 (1.17.0-2025.06.26)

---

The "Strict Tracking Protection Fix" option is no more disabling the download progress.

[AlttiRi]

Interesting that FireMonkey works fine even without "Strict Tracking Protection Fix" option enabled (with the last script version).