UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/70.0.3522.0 Safari/537.36
Steps to reproduce the problem:
1. Compare the expectations in the HTML-AAM spec with the actual exposure via ATK
What is the expected behavior?
What went wrong?
Mapping for the following elements is incorrect:
* abbr: ATK_ROLE_STATIC; not ATK_ROLE_TEXT
* div: ATK_ROLE_SECTION; not ATK_ROLE_PANEL
* embed: ATK_ROLE_EMBEDDED; not ATK_ROLE_PANEL
* figcaption: ATK_ROLE_CAPTION; not ATK_ROLE_PANEL
* iframe: ATK_ROLE_INTERNAL_FRAME; not ATK_ROLE_DOCUMENT_WEB
* legend: ATK_ROLE_LABEL; not ATK_ROLE_TEXT
* mark: ATK_ROLE_STATIC; not ATK_ROLE_TEXT
* meter: ATK_ROLE_LEVEL_BAR; not ATK_ROLE_PROGRESS_BAR
* password input: ATK_ROLE_PASSWORD_TEXT; not ATK_ROLE_ENTRY
* pre: ATK_ROLE_SECTION; not ATK_ROLE_TEXT
* select (size 1): ATK_ROLE_COMBO_BOX; not ATK_ROLE_PUSH_BUTTON
* sub: ATK_ROLE_SUBSCRIPT; not ATK_ROLE_TEXT
* sup: ATK_ROLE_SUPERSCRIPT; not ATK_ROLE_TEXT
* svg root: ATK_ROLE_DOCUMENT_FRAME; not ATK_ROLE_IMAGE
* textarea (readonly): Remove ATK_STATE_EDITABLE
* th (rowheader): ATK_ROLE_ROW_HEADER; not ATK_ROLE_TABLE_ROW_HEADER
* time: ATK_ROLE_STATIC; not ATK_ROLE_TEXT
Additional corrections:
* color input: ATK_ROLE_PUSH_BUTTON; not ATK_ROLE_COLOR_CHOOSER
This is consistent with the implementations of both Gecko and
WebKitGtk. A pull request has been submitted to fix the HTML-AAM.
* layout table objects: ATK_ROLE_SECTION; not ATK_ROLE_PANEL.
While not explicitly stated in the HTML-AAM, this is consistent
with the Core-AAM mapping of tables with role presentation.
Did this work before? N/A
Chrome version: 70.0.3522.0 Channel: n/a
OS Version:
Flash Version:
Comment 1 by bugdroid1@chromium.org
, Aug 16