Contact [email protected] Explainerhttps://open-ui.org/components/accordion.explainer
Specificationhttps://github.com/whatwg/html/pull/9400 Summary This feature adds the ability to construct exclusive accordions using a sequence of HTML <details> elements. It adds a name attribute to the <details> element. When this attribute is used, multiple <details> elements that have the same name form a group. At most one element in the group can be open at once. Blink componentBlink>HTML>Details <https://bugs.chromium.org/p/chromium/issues/list?q=component:Blink%3EHTML%3EDetails> TAG reviewhttps://github.com/w3ctag/design-reviews/issues/866 (design review) TAG review statusIssues addressed Risks Interoperability and Compatibility *Gecko*: Positive (https://github.com/mozilla/standards-positions/issues/831 ) *WebKit*: In development ( https://github.com/WebKit/standards-positions/issues/209) positive standards position and code landed (although a little behind the most recent changes to the proposal) *Web developers*: No signals Got significant feedback from web developers in https://github.com/openui/open-ui/issues/812 . See examples of use on live sites in https://open-ui.org/components/accordion.explainer/#developer-demand-for-exclusive-accordion *Other signals*: WebView application risks Does this intent deprecate or change behavior of existing APIs, such that it has potentially high risk for Android WebView-based applications? no Debuggability Will this feature be supported on all six Blink platforms (Windows, Mac, Linux, Chrome OS, Android, and Android WebView)?Yes Is this feature fully tested by web-platform-tests <https://chromium.googlesource.com/chromium/src/+/main/docs/testing/web_platform_tests.md> ?Yes Flag name on chrome://flags Finch feature namekAccordionPattern Requires code in //chrome?False Tracking bughttps://bugs.chromium.org/p/chromium/issues/detail?id=1444057 Availability expectationHoping to get cross-browser adoption relatively quickly (<12 months) given that it's a small feature that seems to be widely supported. Adoption expectationWider adoption may depend on also doing other changes, like improved stylability of <details> and <summary> elements. Non-OSS dependencies Does the feature depend on any code or APIs outside the Chromium open source repository and its open-source dependencies to function? no Estimated milestones Shipping on desktop 120 Shipping on Android 120 Shipping on WebView 120 Anticipated spec changes Open questions about a feature may be a source of future web compat or interop issues. Please list open issues (e.g. links to known github issues in the project for the feature specification) whose resolution may introduce web compat/interop risk (e.g., changing to naming or structure of the API in a non-backward-compatible way). There may still be some small changes as part of the process of getting https://github.com/whatwg/html/pull/9400 finished, but I hope to implement those before shipping (at least those that happen soon). Link to entry on the Chrome Platform Status https://chromestatus.com/feature/6710427028815872 Links to previous Intent discussionsIntent to prototype: https://groups.google.com/a/chromium.org/g/blink-dev/c/Q1OX6ZA_aaE/m/ALwkAOfHAwAJ This intent message was generated by Chrome Platform Status <https://chromestatus.com/>. -- You received this message because you are subscribed to the Google Groups "blink-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAG0MU3jdK2cMo8_hwyEFQLWUQ9W0xa60uy4wJnAMpZMdBApDfQ%40mail.gmail.com.
