Adblock Plus is probably the reason Firefox and Chrome are such memory hogs

Re:Adblock Plus is probably the reason Firefox and Chrome ar... by alopecoid on Saturday December 27, 2014 @12:23PM (#8803175)

So there's no explicit way to distinguish between "new window" calls from other types of calls? I'm kind of shocked that, with all the effort that's been put into browsers in recent years, that the ability to "create a new window" hasn't been removed entirely from the API without explicit user consent. Again, I can't think of a single site that uses this feature legitimately.

[ Parent | on HN ]

Re:Adblock Plus is probably the reason Firefox and Chrome ar... by cozuya on Saturday December 27, 2014 @12:58PM (#8803281)

If you're talking about actual new windows that are a separate process, those have been blocked by popup blockers for years. As far as popovers that block the screen/annoy you, those are just HTML elements that are positioned on top of normal content - its not a "special" thing backed into the DOM API. There's really no effective way to stop a page from being able to do that unless you disable javascript entirely.

[ Parent | on HN ]

Re:Adblock Plus is probably the reason Firefox and Chrome ar... by nitrogen on Saturday December 27, 2014 @01:16PM (#8803359)

There have been tricks that get popups through, possibly by exploiting browser bugs or opening the popup in one of the few on* handlers where browsers allow them.

[ Parent | on HN ]

Re:Adblock Plus is probably the reason Firefox and Chrome ar... by Steko on Saturday December 27, 2014 @03:29PM (#8803810)

I use strict pop up blocker on firefox which works great. There's a toggle button in case a site doesn't work properly.

https://addons.mozilla.org/en-US/firefox/addon/strict-pop-up...

[ Parent | on HN ]