Changes between Version 5 and Version 13 of Ticket #5584


Ignore:
Timestamp:
08/29/2017 06:45:52 AM (2 years ago)
Author:
trev
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #5584

    • Property Status changed from reviewing to reopened
    • Property Blocked By changed from to 5535
    • Property Priority changed from Unknown to P2
    • Property Ready set
    • Property Milestone changed from to Adblock-Plus-for-Chrome-Opera-next
    • Property Owner set to hfiguiere
  • Ticket #5584 – Description

    v5 v13  
    66|| hg || git || 
    77|| 217eff0504a5 || 48eddbc || 
     8 
     9Make sure that elemHideEmulation is packaged as a module (see #5516). 
    810 
    911=== Included changes === 
     
    2022=== Hints for testers === 
    2123 
    22 * We have changed path for some files. Check the add-on work on overall on all the platform. 
    23 * Issue #5422 and #5436 have fileter test case that were failing. Make sure :-abp-has() still work as advertised. 
    24 * The add-on should work again on Chrome 49 and 50. 
    25 * We can now match element based on CSS properties in their ::before and ::after pseudo-elements. See issue #5339 for details 
    26 * We new detect changes in the DOM which mean we re-run the filters as it goes. Attention should be paid to performance. If there is no `#?#` filters for the domain, this shouldn't occur. Otherwise it should not happen too often. This is issue #5438. 
    27 * Issue #5000 that is not mentioned in this list should be verified. It works now with a combination of #5438 and #5339. Make sure to check the appropriate filter in the issue description. 
     24* Issues #5459, #5460, #5558 implement changes to notification handling. Testing the notification mechanism is non-trivial unfortunately. 
     25* Issues #5079, #5339, #5381, #5422, #5436, #5438, #5516 all affect element hiding emulation functionality, please refer to the descriptions in the respective issues. 
     26* Issue #5000 isn't part of the list but has been resolved implicitly by #5438 and #5339 and should be retested. 
     27* The commits without issue have no impact on the build or affect functionality already covered by one of the issues above.