A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://github.com/w3c/csswg-drafts/issues/9230 below:

[css-display-4] Define how reading-flow interacts with focusable display: contents elements. · Issue #9230 · w3c/csswg-drafts · GitHub

#8589 / #7387 (comment) propose new properties to alter the reading order of the items to follow the layout tree order, rather than the dom order.

However, that is in conflict with #2632 / mozilla/standards-positions#772, in the sense that there doesn't seem to be a good order for display: contents elements that are focusable in a visually-order container.

We need to sort out how these two proposals interact. What is the tab order of a display: contents element inside an element with non-auto reading-order?

cc @rachelandrew @tabatkins @fantasai @dbaron


RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4