NEW 238266
Implement hidden=until-found HTML attribute and beforematch event
https://bugs.webkit.org/show_bug.cgi?id=238266
Summary Implement hidden=until-found HTML attribute and beforematch event
Joey Arhar
Reported 2022-03-23 09:34:08 PDT
This feature was added to the HTML spec here: https://github.com/whatwg/html/pull/7475 Here is an explainer: https://github.com/WICG/display-locking/blob/main/explainers/hidden-content-explainer.md The "until-found" value for the hidden attribute should make the element content-visibility:hidden instead of display:none. When the browser searches for text via find-in-page or ScrollToTextFragment, it should also search for text in hidden=until-found elements. If find-in-page or ScrollToTextFragment want to scroll to a match inside a hidden=until-found element, it should remove the hidden attribute from the element and fire the "beforematch" event on it in order to reveal the match.
Attachments
Radar WebKit Bug Importer
Comment 1 2022-03-23 10:01:02 PDT
Michał Gołębiowski-Owczarek
Comment 2 2025-01-05 04:28:09 PST
As stated in https://bugzilla.mozilla.org/show_bug.cgi?id=1761043, Wikipedia uses this attribute now, which means find in page works much better in Chrome on Android than on iOS. This is something I am hitting on a daily basis as an iOS user.
Tim Nguyen (:ntim)
Comment 3 2025-01-05 16:22:31 PST
Bug 228843 can probably be used as inspiration if someone wants to hack this.
Christian "Schepp" Schaefer
Comment 4 2025-02-17 00:11:16 PST
I've found one more use case where hidden=until-found is very helpful which I described here: https://schepp.dev/posts/rethinking-find-in-page-accessibility-making-hidden-text-work-for-everyone/ I'm aware that this feature is part of Interop 2025 via <details> element, but maybe we can get this quicker than end of this year?
Note You need to log in before you can comment on or make changes to this bug.