gtk2/testsuite/a11y/lockbutton.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
  button1
    "push button"
    parent: window1
    index: 0
    name: Lock
    description: Dialog is unlocked.
Click to prevent further changes
    state: enabled focusable focused sensitive showing visible has-tooltip
    toolkit: gtk
    <AtkComponent>
    layer: widget
    alpha: 1
    <AtkImage>
    image size: -1 x -1
    image description: (null)
    <AtkAction>
    action 0 name: click
    action 0 description: Clicks the button
Add a lockbutton testcase 2011-06-22 03:34:38 +00:00			`window1`
testsuite: Make a11y tests use regular windows 2020-02-14 18:25:23 +00:00			`"frame"`
Add a lockbutton testcase 2011-06-22 03:34:38 +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`
Add a lockbutton testcase 2011-06-22 03:34:38 +00:00			`<AtkComponent>`
Make a11y testsuite pass 2020-02-18 00:44:07 +00:00			`layer: widget`
Add a lockbutton testcase 2011-06-22 03:34:38 +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 lockbutton testcase 2011-06-22 03:34:38 +00:00			`button1`
			`"push button"`
			`parent: window1`
			`index: 0`
Convert GailButton to GtkButtonAccessible This drops the AtkText implementation, and also strips handling of children out. Instead of listening for enter/leave/press/released, just listen for state changes on the widget. 2011-07-02 01:25:53 +00:00			`name: Lock`
Add a lockbutton testcase 2011-06-22 03:34:38 +00:00			`description: Dialog is unlocked.`
			`Click to prevent further changes`
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 sensitive showing visible has-tooltip`
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 lockbutton testcase 2011-06-22 03:34:38 +00:00			`<AtkComponent>`
			`layer: widget`
			`alpha: 1`
			`<AtkImage>`
Convert GailButton to GtkButtonAccessible This drops the AtkText implementation, and also strips handling of children out. Instead of listening for enter/leave/press/released, just listen for state changes on the widget. 2011-07-02 01:25:53 +00:00			`image size: -1 x -1`
Add a lockbutton testcase 2011-06-22 03:34:38 +00:00			`image description: (null)`
			`<AtkAction>`
			`action 0 name: click`
Update a11y test results to match The newly added descriptions show up in the accessible information dumps. 2013-02-04 05:55:43 +00:00			`action 0 description: Clicks the button`