4 ms·

uBlock didn't fix it for me. Also, because the second overlay was huge, I couldn't close it down so I closed the tab instead...

• Ntrails 11y ago
  Maybe it's time to NoScript?
  • iaskwhy 11y ago
    I get the feeling having NoScript can be more annoying that not having it so I have been procrastinating installing it...
    • antsar 11y ago
      Speaking as someone who has NoScript installed... you are sadly correct.
    • gorhill 11y ago
      I use "medium mode" in uBlock[1], which causes only 3rd-party scripts/frames to be blocked, not 1st-party ones. I could read the article fine, I had no idea there were issues with overlays with it, and it otherwise rendered fine. Not blocking 1st-party scripts remove a lot of the tediousness of blocking scripts by default. [1] https://github.com/gorhill/uBlock/wiki/Blocking-mode:-medium-mode https://github.com/gorhill/uBlock/wiki/Blocking-mode:-medium...
      • Vexs 11y ago
        There's also ublock matrix which is noscript but easier to work with.
      • iaskwhy 11y ago
        Thanks for the suggestion, it looks very interesting. And, obviously, thanks for all the work on uBlock Origin, interneting got much less annoying after installing it in every machine I get my hands on. Thanks!
  • StavrosK 11y ago
    Why? Just don't read articles from such annoying sites.
• codingdave 11y ago
  Right click, Inspect Element, Delete. most of those seem to be about 20 divs deep, but usually have a parent div labelled "modal_something", so move up the chain and delete that parent. It is annoying to have to do that, so I only do it if I truly care about reading the page. But once it is in your browser, it is in your control. Use that control.
  • iaskwhy 11y ago
    I do it a lot for Stylebot but only a really small minority of websites deserve that waste of time. It's a good tip, one I tell everyone I know about, most sites I read on a daily basis are highly tweaked by the Inspect Element tool plus Stylebot.