hackademix
[Bug] Current tab (in main window) allow/deny NoScript list overwritten by the latest other focused window
Hello,
Latest version (13.0.6) seem to bring some weird new bugs. Youtube one is already acknowledged (in fact it's not just Youtube, i've several sites displayed with "sidebar?" atm), but unsure for this one: If you have several windows opened, no matter the current tab in the first window, the allow/deny NoScript menu will display the (sub)domains list of the latest focused window instead of the current site you're on.
It seems 100% reproducible. Just open a site in a new window, go back to any tab of the first window and you'll have the (sub)domains list in the NoScript menu of the site opened in the new window. Example: Opening a Twitch stream on the side. You won't be able to allow/deny domains on sites you visit anymore in your main/first window and you'll only have the Twitch ones.
Tested w/ latest Firefox stable version 138.0.4.
I've some troubles reproducing this.
NoScript menu will display the (sub)domains list of the latest focused window instead of the current site you're on.
What does "the current site you're on" vs "the site in the current tab of the last focused window" mean?
In other words, how exactly do you open NoScript's UI without focusing the window where the current site is displayed?
It's "the current site you're on" vs "the latest focused window". Any tab you'd be on in the first window would have the NoScript menu list being the one of the latest focused window before that. E.g.: A Twitch stream on the side in a new window, you go back on a tab from your first window and you'll see the domains from Twitch instead of the current site you're on. If i allowed some from my current tab, it even refreshed the Twitch tab on the side.
Forget the 100% reproducible though. I had the bug when i posted it, even by restarting Firefox iirc, but testing just now, it doesn't occur. I wonder if it has something to do with the other bug with domains being listed with "sidebar?". It's just a display bug that got trigger by i don't know what, where somehow an additional opened window takes the priority and it fails to set back the current window index somewhere maybe when you comes back to the first window. I'll try to be aware if it happens again to what i did in order. Trying to find a proper setup to reproduce it. I just know it's a new one, it never occured before this new version.
Edit: So far (2025-06-16), this didn't reoccur on my side. Really wish i knew what caused it. At least it might just be a really rare case so not too big of a deal.