Benjamin Otte ccdc3ee406 selector: Make :not() selectors not radical ... :not() selectors cannot be radical because the bloomfilter only knows if a value is set in any of the nodes, but cannot determine the opposite (if a value is not set in at least one node), but that would be required for:not() selectors. However, this is very unlikely to happen in the real world, so it's not worth optimizing. Unfortunately, change tracking could know this, so by excluding the :not() selectors from radical changes, the change tracking will now pick them up. If that turns out to be a performance problem, we need to add a special category for radical not filters, so change tracking and bloom filters can deal with them. The testcase demonstrating the problem in widget-factory has been extrated and added.		2020-01-28 02:17:03 +01:00
..
change.test.in
meson.build	Remove the widget-factory test again	2020-01-18 00:27:52 -05:00
test1.css
test1.nodes	change tests: Update test output	2020-01-17 23:47:34 -05:00
test1.ui
test2.css
test2.nodes	change tests: Update test output	2020-01-17 23:47:34 -05:00
test2.ui
test3.css
test3.nodes	change tests: Update test output	2020-01-17 23:47:34 -05:00
test3.ui
test4.css
test4.nodes	selector: Make :not() selectors not radical	2020-01-28 02:17:03 +01:00
test4.ui
test5.css
test5.nodes	Fix a css change testcase	2020-01-18 14:32:55 -05:00
test5.ui	Fix a css change testcase	2020-01-18 14:32:55 -05:00
test-css-change.c