Products · Product
NoScript
Raised as a usability problem by 78 people on Hacker News over 19 years (2008–2026), in 72 threads.
No issue was raised by at least 3 people in 3 threads this year.
Every issue, all time, most people first
Scripted sites need many domains whitelisted to workUnreviewed
20082026- Browsing with JavaScript blocked is exhausting because most websites break without it2026-09-05
- Many websites break or look too broken to read without JavaScript enabled2025-08-29
- Has to whitelist scripts and refresh repeatedly before a site works2025-03-05
Repeatedly enabling scripts per site becomes tedious over timeUnreviewed
20082026- Having to reload sites repeatedly to allow the minimum scripts is a pain2025-12-17
- Finding the right combination of scripts to enable is painful and frustrating2021-01-17
- Spent a lot of time guessing which scripts to enable for sites to work2019-07-11
Unreviewed issues were grouped by machine: Claude Haiku labelled each comment as a usability complaint, named what it's about and summed up the problem in a line, and a small model grouped similar problems. Nobody has checked them by hand. Expect mistakes.
The newest 50 complaints
- Browsing with JavaScript blocked is exhausting because most websites break without it2026-09-05
- Having to reload sites repeatedly to allow the minimum scripts is a pain2025-12-17
- Many websites break or look too broken to read without JavaScript enabled2025-08-29
- Has to whitelist scripts and refresh repeatedly before a site works2025-03-05
- Every new site needs a minute in the NoScript UI before it works2024-04-21
- Whitelisting outgoing connections is annoying and forces users into full-time IT administration2023-10-13
- Newer version's grid-based permission interface was opaque and hard to understand2022-09-23
- Interface doesn't show all scripts loading after initial render, so sites break unexpectedly2022-06-27
- Blocking all scripts by default makes most websites unusable2022-05-10
- Sites show a blank page saying JavaScript is required when scripts are blocked2022-02-21
- Sites need repeated whitelisting before text or embedded content will load2021-09-23
- Pages break until user manually enables sites and reloads repeatedly2021-08-18
- Having to re-enable JavaScript per site is frustrating and tedious2021-04-20
- Finding the right combination of scripts to enable is painful and frustrating2021-01-17
- Sites fail to load until many scripts are manually whitelisted, and checkouts break2020-12-23
- Checkout half-fails, forcing hunting for which of many domains to allow2020-10-08
- Tagging model too limited; fine-grained blocking takes many tags and is harder than point-and-click2020-09-20
- Spent a lot of time guessing which scripts to enable for sites to work2019-07-11
- Complicated add-on interface makes it easy to accidentally enable JavaScript2019-06-20
- Browsing becomes nearly impossible because so many sites rely on JavaScript2019-06-05
- Blocking scripts is frustrating; had to disable NoScript to order plane tickets2019-05-28
- Parents have to call for help when websites don't work after scripts are blocked2019-05-26
- Refreshing three times to find which CDN script is needed2019-04-13
- Icon gives no indication of state, so users forget to re-enable restrictions2019-04-13
- UI change was disruptive and takes time to learn2019-04-13
- Menus replaced by icons, so users must rely on tooltips to operate it2019-04-13
- Commenter says NoScript has a bad UI, comparable to Gmail's2019-04-13
- Sites relying on JavaScript break by default until the user works out which CDN to whitelist2018-12-03
- New NoScript interface is difficult to use after overhaul2018-09-06
- Its interface became more complex than uMatrix's, so the commenter switched2018-01-06
- Browser extension UI changes made it too fiddly to use2018-01-04
- Browser extension broken and unusable after latest update2017-11-29
- Preferences window will not open, blocking export of whitelisted domains2017-11-29
- New interface has a steep learning curve and no documentation to explain it2017-11-22
- Manually enabling scripts on every site takes many clicks and breaks things2017-03-22
- Surfing new sites turns into endless configuration work for each one2017-03-12
- Commenter finds NoScript's UI/UX completely unusable even for a technical user2017-02-14
- Trial and error needed to find which scripts to enable2016-10-03
- Many websites are unusable when JavaScript is blocked2016-10-03
- Must disconnect from internet and let page fail to disable auto-opened website2016-10-02
- Takes a long time to build a usable list of allowed sites2016-10-02
- Spent more time tuning policies than actually browsing the web2016-09-07
- Has to click enable JS for every new page opened2016-08-05
- Too much of a pain to use on mobile, making it impractical2016-06-08
- Can't install it through the usual Firefox add-on store, needs manual workaround2016-06-07
- Sites needing scripts from many domains make whitelisting too tedious2016-05-16
- NoScript users can't see the font URL to whitelist, must inspect the page manually2016-05-10
- Guessing which domains to whitelist for pages to render is slow and frustrating2016-03-17
- Most sites break and become unusable when JavaScript is blocked2016-03-17
- Its added protections broke many websites unpredictably, making the browser unusable for the commenter2016-03-03