Perma accessible/tests/mochitest/elm/test_HTMLSpec.html | Wrong value of propearty 'role' for ['embed@id="embed_png" node', address: [object HTMLEmbedElement], role: text container, address: 0x1343a01c0].got when Gecko 108 merges to Beta on 2022-11-14
Categories
(Core :: Disability Access APIs, defect)
Tracking
()
Tracking | Status | |
---|---|---|
firefox-esr102 | --- | unaffected |
firefox106 | --- | unaffected |
firefox107 | --- | unaffected |
firefox108 | + | fixed |
People
(Reporter: SerbanS, Unassigned)
References
(Regression)
Details
(Keywords: regression)
[Tracking Requested - why for this release]:
[task 2022-11-04T12:25:34.779Z] 12:25:34 INFO - TEST-PASS | accessible/tests/mochitest/elm/test_HTMLSpec.html | Wrong value of property 'role' for ['undefined node', address: [object Text], role: text leaf, name: 'emphasis', address: 0x7f9bba9ec1c0].
[task 2022-11-04T12:25:34.781Z] 12:25:34 INFO - Buffered messages finished
[task 2022-11-04T12:25:34.782Z] 12:25:34 INFO - TEST-UNEXPECTED-FAIL | accessible/tests/mochitest/elm/test_HTMLSpec.html | Wrong value of property 'role' for ['embed@id="embed_png" node', address: [object HTMLEmbedElement], role: text container, address: 0x7f9bbacaf160].got 'text container', expected 'graphic'
[task 2022-11-04T12:25:34.783Z] 12:25:34 INFO - SimpleTest.ok@chrome://mochikit/content/tests/SimpleTest/SimpleTest.js:414:16
[task 2022-11-04T12:25:34.784Z] 12:25:34 INFO - isRole@chrome://mochitests/content/a11y/accessible/tests/mochitest/role.js:199:5
[task 2022-11-04T12:25:34.784Z] 12:25:34 INFO - testAccessibleTree@chrome://mochitests/content/a11y/accessible/tests/mochitest/common.js:486:15
[task 2022-11-04T12:25:34.785Z] 12:25:34 INFO - testElm@chrome://mochitests/content/a11y/accessible/tests/mochitest/common.js:414:21
[task 2022-11-04T12:25:34.785Z] 12:25:34 INFO - doTest@chrome://mochitests/content/a11y/accessible/tests/mochitest/elm/test_HTMLSpec.html:481:14
[task 2022-11-04T12:25:34.786Z] 12:25:34 INFO - Not taking screenshot here: see the one that was previously logged
[task 2022-11-04T12:25:34.786Z] 12:25:34 INFO - TEST-UNEXPECTED-FAIL | accessible/tests/mochitest/elm/test_HTMLSpec.html | No nsIAccessibleImage interface on ['embed@id="embed_png" node', address: [object HTMLEmbedElement], role: text container, address: 0x7f9bbacaf160]
[task 2022-11-04T12:25:34.787Z] 12:25:34 INFO - SimpleTest.ok@chrome://mochikit/content/tests/SimpleTest/SimpleTest.js:414:16
[task 2022-11-04T12:25:34.788Z] 12:25:34 INFO - testAccessibleTree@chrome://mochitests/content/a11y/accessible/tests/mochitest/common.js:470:13
[task 2022-11-04T12:25:34.788Z] 12:25:34 INFO - testElm@chrome://mochitests/content/a11y/accessible/tests/mochitest/common.js:414:21
[task 2022-11-04T12:25:34.789Z] 12:25:34 INFO - doTest@chrome://mochitests/content/a11y/accessible/tests/mochitest/elm/test_HTMLSpec.html:481:14
[task 2022-11-04T12:25:34.789Z] 12:25:34 INFO - TEST-PASS | accessible/tests/mochitest/elm/test_HTMLSpec.html | Wrong value of property 'role' for ['embed@id="embed_html" node', address: [object HTMLEmbedElement], role: internal frame, address: 0x7f9bba9ec080].
Hi Nathan, can you please take a look at this? It may be regressed by 1748585.
Updated•3 years ago
|
Comment 1•3 years ago
|
||
Yup, I'm taking a look at this. It looks like I didn't see the problem in testing Nightly since it's triggered by the browser.opaqueResponseBlocking.syntheticBrowsingContext
pref being set to false - it's true by default on Nightly. When the pref is false, we take a different path when testing an embedded image, which causes the failure. I don't understand exactly how my change might have broken this yet, but it seems related so I'm continuing to investigate.
Comment hidden (Intermittent Failures Robot) |
Comment hidden (Intermittent Failures Robot) |
Updated•3 years ago
|
Comment 4•3 years ago
|
||
This failure did not occur in today's beta-sim: https://treeherder.mozilla.org/jobs?repo=try&group_state=expanded&revision=34adafe31e0c69351f484bfd94787fb4c0489f35
Comment 5•3 years ago
|
||
Yup, since the patch addressing this alt="" bug got backed out for causing this issue (among others), this bug should be fixed. When I re-submit an updated patch for that linked alt="" bug, I'll be sure to preemptively address this issue so the bug doesn't resurface.
Comment 6•3 years ago
•
|
||
This was fixed by backing out Bug 1748585 from Firefox 108 as the above comment states.
![]() |
||
Updated•3 years ago
|
Description
•