Update @eyeo/webext-ad-filtering-solution dependency to 1.3.2
Background
We want to bring in the latest changes to our ad blocking extension engine.
See related Adblock Plus issue at https://gitlab.com/adblockinc/ext/adblockplus/adblockplusui/-/issues/1565.
Dependency changes
- Name: @eyeo/webext-ad-filtering-solution
- New version: 1.3.2 (incl. 1.3.0, 1.3.1)
-
Breaking changes:
- 1.3.0
-
https://jira.eyeo.com/browse/EE-293 - Element hiding emulation filter hits can now also indicate a DOM element removal (i.e.
Filter.remove === true
).
-
https://jira.eyeo.com/browse/EE-293 - Element hiding emulation filter hits can now also indicate a DOM element removal (i.e.
- 1.3.1
-
https://jira.eyeo.com/browse/EE-301 - Fixed:
subscriptions.addDefaults()
no longer throws when no recommendation specific to user's language is available (see #531 (closed)).
-
https://jira.eyeo.com/browse/EE-301 - Fixed:
- 1.3.0
-
Other changes:
- 1.3.0
-
https://jira.eyeo.com/browse/EE-11 - Added
filters.normalize()
. - https://jira.eyeo.com/browse/EE-248 - Added support for domain wildcards in element hiding filters.
- https://jira.eyeo.com/browse/EE-255 - Added support for DOM element removal functionality in element hiding emulation filters.
- https://jira.eyeo.com/browse/EE-285 - Fixed: Missing notification about finished filter list download.
-
https://jira.eyeo.com/browse/EE-11 - Added
- 1.3.1
- https://jira.eyeo.com/browse/EE-294 - Fixed: Unable to unallowlist domains from filter lists in Manifest v3.
- https://jira.eyeo.com/browse/EE-300 - Fixed: Reverted performance regression (see #532 (closed)).
- https://jira.eyeo.com/browse/EE-304 - Fixed: Incorrect handling of first-party requests in third-party frames (see #539 (closed)).
- Manifest v3: Fixed: Removing custom filter also removed corresponding rule in ruleset.
- 1.3.2
-
https://jira.eyeo.com/browse/EE-307 - Fixed:
$document
filters were broken for iFrames (see #552 (closed)).
-
https://jira.eyeo.com/browse/EE-307 - Fixed:
- 1.3.0
Integration changes
-
Development:
- Remove temporary workaround introduced in #531 (closed).
- Add support for DOM element removal filters to developer tools panel.
- Add support for DOM element removal filters to issue report data.
- Remove hardcoded filter list header validation logic and instead use
filters.normalize()
.
Relevant links
None.
Hints for testers
- Verify that #531 (closed), #532 (closed), #539 (closed) and #552 (closed) are still fixed.
- Verify that unallowlisting a domain that is allowlisted via a filter list works as expected.
- Developer tools panel and issue report data should consider DOM element removal element hiding emulation filters.
- Copy-pasting a filter list into the custom filter table should work as expected (e.g. no errors should occur; filter list header should be ignored and not added).
Edited by Thomas Greiner