543532 - mochitest-a11y: accessible/tree/test_combobox.xul fails on osx

Status: NEW

(Core :: Disability Access APIs, defect)

Description

[David Bolter [:davidb] (NeedInfo me for attention)]

For menulist2, we get 3 children but expected 4. I took a quick look in DOMi and the DOM+XBL tree looked right. Filing for future debugging.

Note OSX a11y mochitests are not currently enabled on tinderbox.

Comment 1

[alexander :surkov (:asurkov)]

(In reply to comment #0)
> For menulist2, we get 3 children but expected 4. I took a quick look in DOMi
> and the DOM+XBL tree looked right.

you should inspect accessible tree.

Comment 2

[David Bolter [:davidb] (NeedInfo me for attention)]

(In reply to comment #1)
> (In reply to comment #0)
> > For menulist2, we get 3 children but expected 4. I took a quick look in DOMi
> > and the DOM+XBL tree looked right.
> 
> you should inspect accessible tree.

Yep I realized that after I closed and rebuilt; which blew away my DOMi install for the mochitest profile.

Comment 3

[David Bolter [:davidb] (NeedInfo me for attention)]

Cross-referencing the node tree with the a11y tree, we don't seem to be picking
up the xul:dropmarker; I'm not used to DOMi though... it looks like the
dropmarker xbl:inherits disabled state, so maybe the right fix is to just not
expect the dropmarker (button)?

Comment 4

[(no longer active)]

I seem to be getting this failure on trunk (locally) as well...

Comment 5

[alexander :surkov (:asurkov)]

(In reply to comment #3)
> Cross-referencing the node tree with the a11y tree, we don't seem to be picking
> up the xul:dropmarker; I'm not used to DOMi though... it looks like the
> dropmarker xbl:inherits disabled state, so maybe the right fix is to just not
> expect the dropmarker (button)?

disabled is not a reason to not expose an accessible. It's better to check with DOMi to be sure you deal with cross platform code.

Comment 6

[David Bolter [:davidb] (NeedInfo me for attention)]

I was using DOMi in comment 3 :)

Comment 7

[David Bolter [:davidb] (NeedInfo me for attention)]

(In reply to comment #5)
> disabled is not a reason to not expose an accessible.

true, it is just a state after all.

Comment 8

[Serge Gautherie (:sgautherie)]

What is the exact reported error?
(related to bug 535893?)

Comment 9

[alexander :surkov (:asurkov)]

(In reply to Serge Gautherie (:sgautherie) from comment #8)
> What is the exact reported error?
> (related to bug 535893?)

failed | Different amount of expected children of ['menuitem node', role: combobox option, name: 'item', address: 0x1261a5f80]. - got 1, expected 0.