Changes between Version 22 and Version 23 of Ticket #7003


Ignore:
Timestamp:
10/23/2018 11:37:28 AM (10 months ago)
Author:
mjethani
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #7003 – Description

    v22 v23  
    6363 
    6464=== Hints for testers === 
    65 Test that blocking and whitelisting still works. For example, if there a filter `/foo^$script`, it should block any requests to `https://example.com/foo/bar/script.js` (assuming it's being requested as a script); if there an additional filter `@@||example.com^$script` then the same request should be whitelisted and this should appear in the DevTools panel. 
     65Test that blocking and whitelisting still works. For example, if there's a filter `/foo^$script`, it should block any requests to `https://example.com/foo/bar/script.js` (assuming it's being requested as a script); if there's an additional filter `@@||example.com^$script` then the same request should be whitelisted and this should appear in the DevTools panel. 
    6666 
    67 Note that there is a change in behavior now so that if there is no blocking filter for a URL then no whitelist filters will match. For example, given ''only'' the filter `@@||example.com^$script` (no other filters), requests to `https://example.com/foo/bar/script.js` will not be blocked ''and'' the whitelist filter will ''not'' appear in the DevTools panel (because it did not prevent any blocking). You may have to update some tests to reflect this new behavior. Also note that this does not apply to filters containing one of `$document`, `$elemhide`, `$generichide`, and `$genericblock`; these filters are looked up first, before any blocking filters are looked up, so if they cause an entire document to be whitelisted in some way, they ''will'' appear in the DevTools panel even if there are no matching blocking filters. For example, if only the filter `@@||example.com^$document` exists in the filter list, a request to the URL `https://example.com/foo/bar/script.js` will cause this filter to appear in the DevTools panel. Please test this. 
     67Note that there is a change in behavior now so that if there is no blocking filter for a URL then no whitelist filters will match. For example, given ''only'' the filter `@@||example.com^$script` (no other filters), requests to `https://example.com/foo/bar/script.js` will not be blocked ''and'' the whitelist filter will ''not'' appear in the DevTools panel (because it did not prevent any blocking). You may have to update some tests to reflect this new behavior. Also note that this does not apply to filters containing any one or more of `$document`, `$elemhide`, `$generichide`, and `$genericblock`; these filters are looked up first, before any blocking filters are looked up, so if they cause an entire document to be whitelisted in some way, they ''will'' appear in the DevTools panel even if there are no matching blocking filters. For example, if only the filter `@@||example.com^$document` exists in the filter list, a request to the URL `https://example.com/foo/bar/script.js` will cause this filter to appear in the DevTools panel. Please test this.