Opened on 08/21/2019 at 04:36:52 PM
Closed on 08/27/2019 at 10:37:27 AM
Last modified on 10/08/2019 at 06:08:25 PM
#7512 closed defect (rejected)
Previously invalid rule is now valid
Reported by: | BrentM | Assignee: | |
---|---|---|---|
Priority: | Unknown | Milestone: | |
Module: | Unknown | Keywords: | |
Cc: | Ross, sebastian, greiner | Blocked By: | |
Blocking: | Platform: | Chrome | |
Ready: | no | Confidential: | no |
Tester: | Unknown | Verified working: | no |
Review URL(s): |
Description (last modified by BrentM)
Environment
Windows 10
Chrome 76.0.3809.100
ABP 3.6.2
How to reproduce
- Open the ABP Options page
- Click Advanced
- Enter the following rule into the 'My Filter List' section:
^^SDKLS###!!!!!!! (&^()%^^$%$jhdrfs
Observed behaviour
- Rule is saved
Expected behaviour
Previously, in ABP 3.5.2 when the above rule was saved, an error was generated, and the rule wasn't saved. The error was:
Line 1: '#!!!!!!! (&()%$%$jhdrfs' is not a valid CSS selector
Attachments (0)
Change History (4)
comment:3 in reply to: ↑ 2 Changed on 08/27/2019 at 10:37:27 AM by kzar
- Resolution set to rejected
- Status changed from new to closed
Replying to greiner:
That being said, we could try to prevent the user from adding such filters in the UI because there we retain access to the DOM API, if we think it adds enough value.
Good point, sounds like a good idea to me so I've filed https://gitlab.com/eyeo/adblockplus/abpui/adblockplusui/issues/558
Otherwise I don't think there's much we can do here, so I'll close this.
comment:4 Changed on 09/13/2019 at 11:17:14 AM by booms1
spam
When we moved the filter validation logic we also decided to drop the CSS selector validation while doing so because with manifest v3 we won't be able to use the DOM API in the background page (i.e. in Adblock Plus Core) anymore (see #7423).
That being said, we could try to prevent the user from adding such filters in the UI because there we retain access to the DOM API, if we think it adds enough value.