News for hackers. Stuff that matters.

A comment on Changing Our Approach to Anti-Tracking. Parent comment

Re:Changing Our Approach to Anti-Tracking by Dylan16807 on Thursday August 30, 2018 @01:38PM (#17878800)
Heck, popups still work in Chrome if they clickjack. There's no way to entirely disable popups on a site.
[ Parent | on HN ]
Re:Changing Our Approach to Anti-Tracking by tomxor on Thursday August 30, 2018 @03:14PM (#17879817)
Chrome provides many content settings that tend to toggle between "disabled, ask, allow". It should be possible to provide an option for spawning windows even when originating from a user event (although there isn't one currently).
[ Parent | on HN ]
Re:Changing Our Approach to Anti-Tracking by brennebeck on Saturday September 01, 2018 @10:56PM (#17895264)
Are you saying to have a permission that would ‘disallow, ask, or allow’ me opening new tabs? Because that’s exactly what it sounds like to me.
[ Parent | on HN ]
Re:Changing Our Approach to Anti-Tracking by garmaine on Thursday August 30, 2018 @03:13PM (#17879805)
The browser could just not make any new window as a result of a click in the content area.
[ Parent | on HN ]
Re:Changing Our Approach to Anti-Tracking by askmike on Friday August 31, 2018 @12:31AM (#17882968)
Browsers implement the HTML spec, which allows for this behavior.
[ Parent | on HN ]
Re:Changing Our Approach to Anti-Tracking by adrianN on Friday August 31, 2018 @01:29AM (#17883180)
Browsers have been known to implement the spec only partially.
[ Parent | on HN ]
Re:Changing Our Approach to Anti-Tracking by garmaine on Friday August 31, 2018 @01:34AM (#17883194)
They’re not required to.
[ Parent | on HN ]
Re:Changing Our Approach to Anti-Tracking by feross on Saturday September 01, 2018 @05:28PM (#17893958)
Indeed. Have you seen my site https://theannoyingsite.com/ ?
[ Parent | on HN ]