From 17176013dab9e9dabe8dbae51dbd4645cc9bd5a4 Mon Sep 17 00:00:00 2001 From: Joey Arhar Date: Wed, 9 Jun 2021 15:24:34 -0700 Subject: [PATCH] Added content-visibility:hidden --- source | 19 ++++++++++--------- 1 file changed, 10 insertions(+), 9 deletions(-) diff --git a/source b/source index 5f2b12c14c4..1be7807fcba 100644 --- a/source +++ b/source @@ -76170,12 +76170,13 @@ body { display:none } data-x="fip-active-match">active match using the find-in-page interface.

When find-in-page begins searching for matches, all details elements in the page - which do not have their open attribute set should have - their second slot act as if it is added to the rendering 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 second slot be removed from the rendering again. This entire process must happen - synchronously (and so is not observable to users or to author code).

+ 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).

When find-in-page chooses a new active match, perform the following steps:

@@ -115871,9 +115872,9 @@ details[open] > summary {

The details element's first summary element child, if any, is expected to allow the user to request the details be shown or hidden.

-

The details element's second slot is expected - to be removed from the rendering when the details element does not have an open attribute.

+

The details element's second slot must have the + style "display:block; content-visibility:hidden" when the details + element does not have an open attribute.