1724299 - Implement auto-expanding <details>

Status: NEW

(Core :: Find Backend, enhancement)

Description

[Joey Arhar]

In this HTML spec PR, we are making <details> automatically expand for element fragments and find-in-page: https://github.com/whatwg/html/pull/6466
This way, the user can effectively use find-in-page to search for content hidden inside <details> elements without having to manually expand all of them first.
In order to make it performant, the spec PR also suggests using content-visibility:hidden inside <details>'s user agent shadowdom instead of "removing the slot from the rendering" when <details> are closed.

Comment 1

[BugBot [:suhaib / :marco/ :calixte]]

The Bugbug bot thinks this bug should belong to the 'Firefox::Address Bar' component, and is moving the bug to that component. Please revert this change in case you think the bot is wrong.

Comment 2

[Clara Guerrero ( Need Info Brindusa Tot Please)]

Hi,
Thank you for opening this enhancement. I will set this as New and waiting for the developers opinion about it.

Thanks for your input.

Comment 3

[Drew Willcoxon :adw]

Not sure whether this belongs in Find Toolbar or Core, but auto-expanding when the find toolbar is used sounds like more of the former...

Comment 4

[Bill Goldstein [:aja] (UTC-6)]

FYI: This is now shipping in Chrome.
From Chrome 97 announcement at https://blog.chromium.org/2021/11/chrome-97-webtransport-new-array-static.html

"Auto-expand Details Elements

Closed details elements are now searchable and can now be linked to. These hidden elements will also automatically expand when find-in-page, ScrollToTextFragment, and element fragment navigation are used."

Comment 7

[Jim Lewis]

Currently works in both Chrome and Edge

For EDA log files that are 180K lines long, using <summary>/<details> to hide information is important. Yet when our build summary report (similar to a JUnit test report) shows that a test failed, we need to be able to quickly go to the log information for that test failure. Putting the link inside of the <details> allows us to jump to the appropriate place and provide the detailed information.

Comment 10

[max]

Expandable on search <details> are recommended from the standpoint of accessibility
https://fosdem.org/2023/schedule/event/a11y_eaa_bfsg_wcag_wai_aria_wtf/

Comment 11

[Lillie Glover]

It sounds like you're discussing a proposed change to the HTML specification regarding the behavior of the <details> element. Specifically, the change aims to automatically expand <details> elements for element fragments and find-in-page functionality.

Here's a breakdown of the key points you mentioned:

Automatic Expansion for Element Fragments and Find-in-Page:
The proposed change seeks to make <details> elements automatically expand when used with element fragments and find-in-page functionality. This would enhance user experience by allowing users to search for content within <details> elements without manually expanding each of them first. 

Performance Optimization Using content-visibility:hidden:
To optimize performance, the proposed specification suggests using content-visibility: hidden inside the <details> element's user agent shadow DOM. This is proposed as an alternative to "removing the slot from the rendering" when <details> elements are closed. Using content-visibility: hidden can help improve rendering performance by skipping the rendering of hidden content until it becomes visible. also look at https://www.mtmisverification.com/

Comment 12

[Lillie Glover]

(In reply to Lillie Glover from comment #11)

It sounds like you're discussing a proposed change to the HTML specification regarding the behavior of the <details> element. Specifically, the change aims to automatically expand <details> elements for element fragments and find-in-page functionality. also look at https://mtmisverification.com/

Thank for the info