gtk2/testsuite/a11y/range.txt

window1
  "frame"
  index: 0
  state: enabled resizable sensitive showing visible
  toolkit: gtk
  <AtkComponent>
  layer: widget
  alpha: 1
  unnamed-GtkContainerAccessible-0
    "panel"
    parent: window1
    state: enabled sensitive showing visible
    toolkit: gtk
    <AtkComponent>
    layer: widget
    alpha: 1
  grid1
    "panel"
    parent: window1
    index: 0
    state: enabled horizontal sensitive showing visible
    toolkit: gtk
    <AtkComponent>
    layer: widget
    alpha: 1
    scale1
      "slider"
      parent: grid1
      index: 0
      description: 45.5
      state: enabled focusable focused horizontal sensitive showing visible
      toolkit: gtk
      <AtkComponent>
      layer: widget
      alpha: 1
      <AtkValue>
      minimum value: 0.500000
      maximum value: 99.500000
      current value: 45.500000
    scrollbar1
      "scroll bar"
      parent: grid1
      index: 1
      state: enabled horizontal sensitive showing visible
      toolkit: gtk
      <AtkComponent>
      layer: widget
      alpha: 1
      <AtkValue>
      minimum value: 0.500000
      maximum value: 99.500000
      current value: 45.500000
Add a test involving ranges 2011-06-19 21:58:57 +00:00			`window1`
testsuite: Make a11y tests use regular windows 2020-02-14 18:25:23 +00:00			`"frame"`
Add a test involving ranges 2011-06-19 21:58:57 +00:00			`index: 0`
a11y tests: Ignore "active" flag on toplevel All the a11y tests were failing for me with a window state diff like this: - state: active enabled resizable sensitive showing visible + state: enabled resizable sensitive showing visible I guess the windows in the CI always gets the focus, but not when I run it here. Generally focus seems asynchronous and hard to rely on so I just made the test ignore the active state on toplevels. 2020-02-04 14:01:48 +00:00			`state: enabled resizable sensitive showing visible`
Change the toolkit attribute from gail to gtk Update test results to match. 2011-07-02 22:44:12 +00:00			`toolkit: gtk`
Dump AtkComponent properties Note that the spatial aspects of AtkComponent are all dependent on fonts and other environmental factors, thus we only dump the little bits outside of that. 2011-06-19 23:51:15 +00:00			`<AtkComponent>`
Make a11y testsuite pass 2020-02-18 00:44:07 +00:00			`layer: widget`
Dump AtkComponent properties Note that the spatial aspects of AtkComponent are all dependent on fonts and other environmental factors, thus we only dump the little bits outside of that. 2011-06-19 23:51:15 +00:00			`alpha: 1`
testsuite: Make a11y tests use regular windows 2020-02-14 18:25:23 +00:00			`unnamed-GtkContainerAccessible-0`
			`"panel"`
			`parent: window1`
			`state: enabled sensitive showing visible`
			`toolkit: gtk`
			`<AtkComponent>`
			`layer: widget`
			`alpha: 1`
Add a scrollbar to the range testcase 2011-06-21 23:12:55 +00:00			`grid1`
			`"panel"`
Add a test involving ranges 2011-06-19 21:58:57 +00:00			`parent: window1`
			`index: 0`
Add a scrollbar to the range testcase 2011-06-21 23:12:55 +00:00			`state: enabled horizontal sensitive showing visible`
Change the toolkit attribute from gail to gtk Update test results to match. 2011-07-02 22:44:12 +00:00			`toolkit: gtk`
Dump AtkComponent properties Note that the spatial aspects of AtkComponent are all dependent on fonts and other environmental factors, thus we only dump the little bits outside of that. 2011-06-19 23:51:15 +00:00			`<AtkComponent>`
			`layer: widget`
			`alpha: 1`
tests: Update the expected a11y dump results Keep in sync with the current tree. The changes are mostly caused by updates in the internal hierarchy of composite widgets, and the fact that the order in which the widget tree is traversed is not exactly stable. 2018-04-13 18:19:02 +00:00			`scale1`
			`"slider"`
Add a scrollbar to the range testcase 2011-06-21 23:12:55 +00:00			`parent: grid1`
			`index: 0`
tests: Update the expected a11y dump results Keep in sync with the current tree. The changes are mostly caused by updates in the internal hierarchy of composite widgets, and the fact that the order in which the widget tree is traversed is not exactly stable. 2018-04-13 18:19:02 +00:00			`description: 45.5`
a11y tests: Update expected results The changes here are all related to initial focus. 2019-03-17 01:49:24 +00:00			`state: enabled focusable focused horizontal sensitive showing visible`
Change the toolkit attribute from gail to gtk Update test results to match. 2011-07-02 22:44:12 +00:00			`toolkit: gtk`
Add a scrollbar to the range testcase 2011-06-21 23:12:55 +00:00			`<AtkComponent>`
			`layer: widget`
			`alpha: 1`
tests: Update the expected a11y dump results Keep in sync with the current tree. The changes are mostly caused by updates in the internal hierarchy of composite widgets, and the fact that the order in which the widget tree is traversed is not exactly stable. 2018-04-13 18:19:02 +00:00			`<AtkValue>`
			`minimum value: 0.500000`
			`maximum value: 99.500000`
			`current value: 45.500000`
			`scrollbar1`
			`"scroll bar"`
Add a scrollbar to the range testcase 2011-06-21 23:12:55 +00:00			`parent: grid1`
			`index: 1`
Update a11y test results 2020-04-09 04:41:30 +00:00			`state: enabled horizontal sensitive showing visible`
Change the toolkit attribute from gail to gtk Update test results to match. 2011-07-02 22:44:12 +00:00			`toolkit: gtk`
Add a scrollbar to the range testcase 2011-06-21 23:12:55 +00:00			`<AtkComponent>`
			`layer: widget`
			`alpha: 1`
Add GtkScrollbarAccessible When GtkScrollbar stopped being a GtkRange, GtkRangeAccessible stopped working for scrollbars. Update a11y tests to match. 2020-04-03 19:14:26 +00:00			`<AtkValue>`
			`minimum value: 0.500000`
			`maximum value: 99.500000`
			`current value: 45.500000`