Changes between Initial Version and Version 1 of Ticket #7104, comment 8


Ignore:
Timestamp:
11/21/2018 12:50:21 PM (10 months ago)
Author:
Ross
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #7104, comment 8

    initial v1  
    11You're right, it's a blocking filter. I feel like I gave a bad explaination, I've updated the example above. I think there might actually be two issues here (but I also might be wrong): 
    22 
    3 1. Firefox still hides/blocks an image that was previously the target of the filter, but is no longer (the filter changed). So in the updated example above, `test2.jpg` is still being hidden/blocked even though the filter is now `test1.jpg` instead of `test*.jpg`. The ABP icon also indicates just 1 blocked item. This is fixed after closing/reopening the tab. 
     31. Firefox still hides/blocks an image that was previously the target of the filter, but is no longer (the filter changed). So in the updated example above, `test2.jpg` is still being hidden/blocked even though the filter is now `test1.jpg` instead of `test*.jpg`. The ABP icon also indicates just 1 blocked item. This is fixed after closing/reopening the tab. Also "fixed" when removing the filters. 
    44 
    552. The second issue is that, when inspecting the image element pointing at `test1.jpg` in the example above, the number of `display:none` rules applied to it is dependent on the number of times the page has been refreshed. Each refresh adds another. This isn't exactly incorrect, as the image is hidden correctly. However the extra rules on page refresh seems to indicate something weird is happening somewhere? Chrome does not have the same behaviour.