I am implementing the auto-expanding details elements feature in Chromium, and I would like to hear WebKit's position on the feature.

Chromestatus entry: https://chromestatus.com/feature/5032469667512320

Spec:

- https://github.com/whatwg/html/pull/6466

- https://html.spec.whatwg.org/multipage/interaction.html#interaction-with-details

Explainer: https://github.com/WICG/display-locking/blob/main/explainers/auto-expanding-details-explainer.md

WebKit bug: https://bugs.webkit.org/show_bug.cgi?id=228843

Today, users can’t search for content inside details elements when they are closed. If the user wants to search the page for content inside details elements with find-in-page, then they have to manually expand every details element in the page before they use find-in-page.

This feature makes the hidden contents of closed details elements searchable by find-in-page and makes the browser automatically open them when trying to scroll to their hidden contents so that users can always search inside them.

In addition to find-in-page, this feature should also work for Element fragments (navigating to a hash with an element id) and ScrollToTextFragment in order to make content hidden inside <details> elements more findable, searchable, and shareable.