Changes between Version 6 and Version 7 of Ticket #492


Ignore:
Timestamp:
09/16/2015 07:03:48 AM (5 years ago)
Author:
sebastian
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #492

    • Property Summary changed from Implement popup blocking in Safari to Implement content blockers to block popups and XMLHttpRequests
    • Property Owner sebastian deleted
    • Property Priority changed from P3 to P4
  • Ticket #492 – Description

    v6 v7  
    11=== Background === 
    2 `$popup` filters aren't implemented in Safari yet. Hence users still see popup ads. 
     2Popups and XMLHttpRequests aren't blocked on Safari, since this wasn't possible so far. However, Safari 9 introduces [https://www.webkit.org/blog/3476/content-blockers-first-look/ content blockers] that lift these limitations. Though this mechanism has quite some other limitations and issues. 
     3 
     4So we might want to stick to the old mechanism based on the `beforeload` DOM event for other means of request blocking, while using the new mechanism to block popups and XMLHttpRequests.  
    35 
    46=== What to change === 
    5 Implement popup blocking for Safari. Therefore move the Chrome specific code to the abstraction layer and add an implementation for Safari, in order to share the code doing the actual blocking. 
     7Use content blockers on Safari 9+ to block popups and XMLHttpRequests.