Re: [csswg-drafts] For the Accessibility API visibility:visible within visibility:hidden is problematic (#6123)

@Loirooriol 

> Why not treat it like when having a ...

In my opinion, such a warning should be placed with every problematic CSS property

> display: table-cell with a display: block parent, if that's not broken?

No. In no browser that I know of, nor according to the specification, does display have any effect on the Accessibility API tree (except, of course, display:none). I.e. neither display:block turns a table into a non-table nor display:table-cell turns a non-table element into a table cell. There is only Chrome's decision to submit a table, fully created with all table property of CSS, as a layout table to the Accessibility API. However, this is firstly not a data table and secondly the tree is not broken by this, since it is submitted as a full table. Furthermore, I think this is a bug of the browser (https://github.com/FreedomScientific/VFO-standards-support/issues/344).


-- 
GitHub Notification of comment by JAWS-test
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6123#issuecomment-803511258 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Sunday, 21 March 2021 04:41:07 UTC