gtk2/testsuite/css/change/test4.nodes

window.background:dir(ltr)    
  box.horizontal:dir(ltr)    name
    label.a:dir(ltr)    class|name|hover
    label.b:dir(ltr)    class|name|hover|backdrop
    label.c:dir(ltr)    class|name|parent-name|parent-hover
    label.d:dir(ltr)    class|name|parent-name|parent-hover|parent-backdrop
    label.e.f:dir(ltr)    class|name|parent-name|parent-hover|parent-backdrop
change tests: Update test output Some of these test cases involve :not, and thus are affected by our now correct handling of it for change computation. All of them are affected by the window now being visible. 2020-01-17 22:57:37 +00:00			`window.background:dir(ltr)`
Add testcases for css change flags Add various tests for the change flag computation that we do in the css selector tree. test1: Just test the basic machinery of this test test2: Trigger every change flag at least once test3: Test that multiple states combine as expected test4: Test negations (known to produce wrong results) test5: Test a complex selector (not producing the expected output atm) widget-factory.ui: The real thing: widget-factory+Adwaita. Note that this expedts to be run with GSETTINGS_BACKEND=memory Note that test4 checks the wrong results that we currently produce for selectors involving :not. It will have to be updated when we fix the handling of :not. The widget-factory.ui testcase will certainly also be affected. 2020-01-17 01:04:00 +00:00			`box.horizontal:dir(ltr) name`
change tests: Update test output Some of these test cases involve :not, and thus are affected by our now correct handling of it for change computation. All of them are affected by the window now being visible. 2020-01-17 22:57:37 +00:00			`label.a:dir(ltr) class\|name\|hover`
			`label.b:dir(ltr) class\|name\|hover\|backdrop`
			`label.c:dir(ltr) class\|name\|parent-name\|parent-hover`
			`label.d:dir(ltr) class\|name\|parent-name\|parent-hover\|parent-backdrop`
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-27 01:49:36 +00:00			`label.e.f:dir(ltr) class\|name\|parent-name\|parent-hover\|parent-backdrop`