Re: [csswg-drafts] [css-a11y][css-display] display: contents; strips semantic role from elements (#3040)

That visual Can I Use table implies all browsers have been broken in the same way.

All browsers ironed out the broader `display: contents` semantics issues many versions / years ago (barring a 113-114 Chrome regression). Safari has caught up as of v17 (with one known outstanding issue for headings: https://bugs.webkit.org/show_bug.cgi?id=261978).

Where all browsers are struggling is with interactive elements that have `display: contents`, including Safari (I filed a PR with Can I Use), owing to some disagreement on how to interpret the spec. As such, there is a request for position by Chrome from each engine:
* Mozilla: https://github.com/mozilla/standards-positions/issues/772
* WebKit: https://github.com/WebKit/standards-positions/issues/164

Which has lead to this WHATWG proposal:
https://github.com/whatwg/html/pull/9425

In other words, this may need to be coordinated with WHATWG as it appears to be running at the problem as well.

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


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

Received on Saturday, 7 October 2023 21:45:06 UTC