Skip to content

Commit

Permalink
Allow elements with display:contents to be focusable
Browse files Browse the repository at this point in the history
This aligns HTML with the conclusion in w3c/csswg-drafts#2632 that elements with CSS `display: contents` should be focusable just like normally-rendered elements. It fixes a piece of #1837.
  • Loading branch information
dbaron authored Jan 31, 2024
1 parent 8c489cb commit 921b688
Showing 1 changed file with 7 additions and 2 deletions.
9 changes: 7 additions & 2 deletions source
Original file line number Diff line number Diff line change
Expand Up @@ -78799,8 +78799,8 @@ dictionary <dfn dictionary>ToggleEventInit</dfn> : <span>EventInit</span> {

<li>the element is not <span>inert</span>;</li>

<li>the element is either <span>being rendered</span> or <span>being used as relevant canvas
fallback content</span>.</li>
<li>the element is either <span>being rendered</span>, <span>delegating its rendering to its
children</span>, or <span>being used as relevant canvas fallback content</span>.</li>
</ul>
<td headers="td-fa-1 th-fa-dom-rep">
The element itself.
Expand Down Expand Up @@ -130792,6 +130792,11 @@ console.assert(container.firstChild instanceof SuperP);
<p class="note">This specification does not define the precise timing for when the intersection is
tested, but it is suggested that the timing match that of the Intersection Observer API. <ref>INTERSECTIONOBSERVER</ref></p>

<p>An element is <dfn>delegating its rendering to its children</dfn> if it is not <span>being
rendered</span> but its children (if any) could <span data-x="being rendered">be rendered</span>,
as a result of CSS 'display: contents', or some equivalent in other styling languages.
<ref>CSSDISPLAY</ref></p>

<hr>

<p>User agents that do not honor author-level CSS style sheets are nonetheless expected to act as
Expand Down

0 comments on commit 921b688

Please sign in to comment.