forked from AuroraMiddleware/gtk
ccdc3ee406
: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. |
||
---|---|---|
.. | ||
adjacent-states.css | ||
adjacent-states.nodes | ||
adjacent-states.ui | ||
bloomfilter-not.css | ||
bloomfilter-not.nodes | ||
bloomfilter-not.ui | ||
colornames.css | ||
colornames.nodes | ||
colornames.ui | ||
currentcolor.css | ||
currentcolor.nodes | ||
currentcolor.ui | ||
font.css | ||
font.nodes | ||
font.ui | ||
gradient.css | ||
gradient.nodes | ||
gradient.ui | ||
gtk.css | ||
inherit.css | ||
inherit.nodes | ||
inherit.ui | ||
label.css | ||
label.nodes | ||
label.ui | ||
meson.build | ||
nth-child.css | ||
nth-child.nodes | ||
nth-child.ui | ||
style.test.in | ||
test-css-style.c | ||
test-css-style.gresource.xml |