Benjamin Otte 495eaf31d4 css: Use the bloom filter for change matching ... Instead of just doing radical change matching on the node itself, also consider the parent nodes via the bloom filter. This means a radical change is now also one where the parent name/id/classes change, but since that's considered a radical change on the parent already, those things are slow anyway. Improves the benchmark times for CSS validation during backdrop transitions in widget-factory from 45ms to 35ms on my machine.		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	css: Use the bloom filter for change matching	2020-01-28 02:17:03 +01:00
test5.ui	Fix a css change testcase	2020-01-18 14:32:55 -05:00
test-css-change.c