Accessibility role of `<input type="image"> becomes "text container" when styled as `display: inline-block;`

RESOLVED FIXED in Firefox 68

Status

()

defect
P2
normal
RESOLVED FIXED
4 months ago
4 months ago

People

(Reporter: mbrodesser, Assigned: emilio)

Tracking

68 Branch
mozilla68
Points:
---
Dependency tree / graph

Firefox Tracking Flags

(firefox68 fixed)

Details

Attachments

(2 attachments)

Reproduction steps:

  1. Add display: inline-block; to input elements (done by the attached patch).

  2. Run ./mach test accessible/tests/mochitest/elm/test_HTMLSpec.html, it'll fail.

Expected result: the test passes and the form has a child "pushbutton".
Actual result: the test fails and the form has a child "text container".

Blocks: 1539469
Version: unspecified → 68 Branch

Fails on Nightly 68.0a1, but probably also earlier versions.

Easier repro is just opening data:text/html,<input type="image" style="display: inline-block"><input type="image">, and see how the role differs in the accessibility inspector.

Ethan, Alex, do you know off-hand what's the code which deals with this? I'm happy to submit a patch to fix it.

Flags: needinfo?(surkov.alexander)
Flags: needinfo?(eitan)
Assignee: nobody → emilio
Flags: needinfo?(surkov.alexander)
Flags: needinfo?(eitan)
Pushed by ealvarez@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/b5298ae13542
The role of a broken input[type="image"] doesn't depend on its display value. r=surkov,eeejay
Priority: -- → P2
Status: NEW → RESOLVED
Closed: 4 months ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla68
You need to log in before you can comment on or make changes to this bug.