diff --git a/source b/source index c08f45cedaf..53b88ce4931 100644 --- a/source +++ b/source @@ -3757,6 +3757,12 @@ a.setAttribute('href', 'https://example.com/'); // change the content attribute
The following term is defined in CSS Containment:
+ +While currentNode has a parent node:
+While currentNode has a parent node within the flat tree:
If the open
attribute is not set on
- currentNode, then Set
+ currentNode, then set
the open
attribute on currentNode to the
empty string.
Otherwise, set currentNode to the parent node of - currentNode within the flat tree.
Issue #3539 tracks
+ standardizing how find-in-page underlies the currently-unspecified window.find()
API.
details
When find-in-page begins searching for matches, all details
elements in the page
- which do not have their open
attribute set should have the
- skipped contents of their
- second slot become accessible. without modifying the open
- attribute in order to make find-in-page able to search through it. After find-in-page finishes
- searching for matches, those details
elements should have their contents become
- skipped again. This entire process must happen synchronously (and so is not observable to users or
- to author code).
open
attribute set should have
+ the skipped contents of their second slot become
+ accessible, without modifying the open
attribute, in
+ order to make find-in-page able to search through it. After find-in-page finishes searching for
+ matches, those details
elements should have their contents become skipped again.
+ This entire process must happen synchronously (and so is not observable to users or to author
+ code).
When find-in-page chooses a new active match, perform the following steps:
@@ -76190,10 +76202,6 @@ body { display:none } revealing algorithm on node. -Issue #3539 tracks
- standardizing how find-in-page underlies the currently-unspecified window.find()
API.
The find-in-page process is invoked in the context of a document, and may have an effect on @@ -115873,12 +115881,18 @@ details[open] > summary { expected to allow the user to request the details be shown or hidden.
The details
element's second slot is expected
- to have its style
attribute set to "display:block;
- content-visibility:hidden" when the details
element does not have an open
attribute. When it does have the style
attribute set to "display:
+ block; content-visibility: hidden;
when the details
element does not have an
+ open
attribute. When it does have the open
attribute, the style
attribute is expected to be removed from the second slot.
Because the slots are hidden inside a shadow tree, this style
attribute is not directly visible to author code, and alternate
+ implementation strategies are possible. Its impacts, however, are visible. Notably, the choice of
+ content-visibility: hidden
instead of, e.g., display:
+ none
, impacts the results of various APIs that query layout information.