Page 1 of 1
Trying to navigate a recent Twitch.tv change that seems to cause some necessary scripts to get filtered
Posted: Sun May 10, 2026 7:50 pm
by Yeti
Using Waterfox 6.6.12/NoScript 13.6.16, started seeing the following a few days ago:
- Some, but not all, elements of the Twitch UI no longer respond to clicks; e.g., the gear menu below chat, the gear menu to adjust video settings within the video playback area.
- A placeholder bottom left of the browser window Noscript says is for https :// s.amazon-adsystem.com/iui3?pid=a30f442a-e833-4300-a302-987199caf562
- If I temp disable restrictions, all the UI controls work as I'd expect.
I assume Twitch has moved some javascript or other functionality onto that URL that was previously hosted elsewhere, but I'm loathe to whitelist that domain since it's (afaik) Amazon's ad service network.
I also assume I could whitelist that specific URL, but I don't really have a handle on what risks that might have (e.g., if the value of pid changes regularly, or if that url can serve different things depending on the value passed for pid)
Would be interested in any recommendations on how to handle this.
Edit-
If it helps this is how noscript reports viewing a stream:

Re: Trying to navigate a recent Twitch.tv change that seems to cause some necessary scripts to get filtered
Posted: Mon May 11, 2026 4:17 am
by barbaz
Yeti wrote: ↑Sun May 10, 2026 7:50 pm
- Some, but not all, elements of the Twitch UI no longer respond to clicks; e.g., the gear menu below chat, the gear menu to adjust video settings within the video playback area.
- A placeholder bottom left of the browser window Noscript says is for
Sounds similar to
viewtopic.php?p=108516#p108516 . If the placeholder(s) for stuff you want to keep blocked, try closing the NoScript placeholder(s). For a more persistent effect you can try the user script in
viewtopic.php?p=104621#p104621
EDIT Actually, maybe try NoScript
latest development build 13.6.19.901 or later before anything else, this version contains a related change to be much more selective about when to pop2top.
Re: Trying to navigate a recent Twitch.tv change that seems to cause some necessary scripts to get filtered
Posted: Fri May 15, 2026 5:21 pm
by Yeti
barbaz wrote: ↑Mon May 11, 2026 4:17 am
Yeti wrote: ↑Sun May 10, 2026 7:50 pm
- Some, but not all, elements of the Twitch UI no longer respond to clicks; e.g., the gear menu below chat, the gear menu to adjust video settings within the video playback area.
- A placeholder bottom left of the browser window Noscript says is for
Sounds similar to
viewtopic.php?p=108516#p108516 . If the placeholder(s) for stuff you want to keep blocked, try closing the NoScript placeholder(s). For a more persistent effect you can try the user script in
viewtopic.php?p=104621#p104621
EDIT Actually, maybe try NoScript
latest development build 13.6.19.901 or later before anything else, this version contains a related change to be much more selective about when to pop2top.
I see that 3.6.19 is now available to update to, so I've done that. No change in behavior that I see.
As for collapsing the placeholder, maybe I'm misunderstanding. If I click on the placeholder I get this:
If I select collapse blocked objects and hit ok, nothing happens even if I reload the page (and if I click on the placeholder again the options selected are back to the defaults pictured. No combination of adjusting the checkboxes seems to do anything different either.
If you'd like we can move the discussion to that other thread so it's all in one place.
Re: Trying to navigate a recent Twitch.tv change that seems to cause some necessary scripts to get filtered
Posted: Fri May 15, 2026 5:32 pm
by Yeti
Didn't realize I was logged out there, oops.
Wanted to add that userscript you linked did work.
Re: Trying to navigate a recent Twitch.tv change that seems to cause some necessary scripts to get filtered
Posted: Fri May 15, 2026 7:34 pm
by barbaz
Yeti wrote: ↑Fri May 15, 2026 5:32 pm
Didn't realize I was logged out there, oops.
Fixed.
Yeti wrote: ↑Fri May 15, 2026 5:32 pm
Wanted to add that userscript you linked did work.

Thanks for reporting back, glad it helped.