Open Bug 890795 Opened 7 years ago Updated 7 days ago

Intermittent TEST-UNEXPECTED-FAIL | events/test_focus_autocomplete.xhtml,test_focus_autocomplete.xul | uncaught exception - NS_ERROR_ILLEGAL_VALUE: Component returned failure code: 0x80070057 (NS_ERROR_ILLEGAL_VALUE) [nsIAccessible.

Categories

(Core :: Disability Access APIs, defect, P3)

x86
macOS
defect

Tracking

()

REOPENED
Tracking Status
firefox24 --- disabled
firefox25 --- disabled
firefox26 --- disabled

People

(Reporter: cbook, Unassigned)

References

()

Details

(Keywords: intermittent-failure, Whiteboard: [test disabled on Linux and Windows][leave open][mac2020_1] )

https://tbpl.mozilla.org/php/getParsedLog.php?id=25006548&tree=Mozilla-Inbound

Ubuntu VM 12.04 mozilla-inbound debug test mochitest-other on 2013-07-07 23:06:53 PDT for push 8c48deec0349

slave: tst-linux32-ec2-103

lots of tests fail with

ERROR TEST-UNEXPECTED-FAIL | chrome://mochitests/content/a11y/accessible/tests/mochitest/events/test_focus_autocomplete.xul | uncaught exception - NS_ERROR_ILLEGAL_VALUE: Component returned failure code: 0x80070057 (NS_ERROR_ILLEGAL_VALUE) [nsIAccessible.getChildAt] at chrome://mochitests/content/a11y/accessible/tests/mochitest/events/test_focus_autocomplete.xul:274
Trev, any chance you could take a look at this? Seems like test_focus_autocomplete.xul has been more failure-prone in general lately.
Flags: needinfo?(trev.saunders)
So the problem seems to be that the tree of options gets focused before it has children for the current options.  Alex do you think we should just wait for focus event as well as options to be created maybe?
Flags: needinfo?(trev.saunders) → needinfo?(surkov.alexander)
(In reply to Trevor Saunders (:tbsaunde) from comment #41)
> So the problem seems to be that the tree of options gets focused before it
> has children for the current options.  Alex do you think we should just wait
> for focus event as well as options to be created maybe?

If I understand right then we should fire focus event for XUL tree and then focus event for current option when it's created. If the tree is part of autocomplete then focus should probably go (or stay) into (in) autocomplete. Can you describe please in details what supposedly happens here, I think we want to have Jamie's option.
(In reply to Trevor Saunders (:tbsaunde) from comment #41)
> So the problem seems to be that the tree of options gets focused before it
> has children for the current options.  Alex do you think we should just wait
> for focus event as well as options to be created maybe?

so actually it doesn't seem to be quiet that simple if I log focus events instead of just seeing what happens when we try and get the accessible I see that the last focus event goes to the anon html:input for the xul autocomplete