Opened on 10/07/2016 at 10:09:34 AM
Closed on 10/07/2016 at 10:43:49 AM
#4501 closed defect (fixed)
Filters with key 0 stay "unconditional" even after an exception is added
Reported by: | trev | Assignee: | trev |
---|---|---|---|
Priority: | P1 | Milestone: | |
Module: | Core | Keywords: | |
Cc: | Blocked By: | ||
Blocking: | #4450 | Platform: | Unknown / Cross platform |
Ready: | yes | Confidential: | no |
Tester: | Unknown | Verified working: | no |
Review URL(s): |
Description
How to reproduce
- With a completely empty filter list, add ##test and then example.com#@#test.
- Open example.com.
Observed behaviour
The filter ##test still applies on example.com. The code which should mark it as no more unconditional fails because its filter key is 0.
Expected behaviour
The filter ##test should no longer apply.
Attachments (0)
Change History (3)
Note: See
TracTickets for help on using
tickets.
A commit referencing this issue has landed:
Issue 4501 - Fix treatment of element hiding filters with filter key 0