Changes between Initial Version and Version 5 of Ticket #748


Ignore:
Timestamp:
07/07/2014 09:13:42 AM (5 years ago)
Author:
trev
Comment:

Note that this feature has been discussed a while ago for Firefox where it is more straightforward to implement. The problem is that blocking all inline scripts without distinguishing between them doesn't seem to be a useful feature. While it will allow getting rid of some anti-adblock messages, in 99% of the cases it will also break the website as a side-effect.

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #748

    • Property Status changed from new to closed
    • Property Cc mapx added
    • Property Component changed from Unknown to Platform
    • Property Summary changed from Implement new javascript blocking to Implement blocking of inline JavaScript
    • Property Platform changed from Unknown to Chrome
    • Property Resolution changed from to invalid
  • Ticket #748 – Description

    initial v5  
    1 Implement javascript blocking as described in 
    2 [https://github.com/gorhill/httpswitchboard/wiki/Blocking-javascript-execution-reliably-in-Chromium-based-browsers] 
     1Blocking inline JavaScript is possible in Chrome, by injecting a fake `Content-Security-Policy` header into the server response for particular websites. Maybe this possibility should be used in Adblock Plus.