[w3ctag/design-reviews] improvements to <details> styling (widget structure) (Issue #965)

こんにちは TAG-さん!

I'm requesting a TAG review of improvements to `<details>` styling that address styling of the widget structure.

This is a set of changes to make the `<details>` and `<summary>` elements more stylable, with the overall goal of making issues with styleability no longer be an obstacle that prevents the use of HTML's built-in elements for this type of widget.

  - Explainer for this set of work: https://dbaron.github.io/details-styling/phase-1.md
    - Also: Earlier explainer for scoping out the overall project: https://dbaron.github.io/details-styling/ ; there may be a later phase to address marker styling but that is independent from this work to address styling the main structure of the widget.
  - HTML Specification URL: https://github.com/whatwg/html/pull/10265
  - CSS specification URL: https://drafts.csswg.org/css-pseudo-4/#details-content-pseudo
  - Tests: https://wpt.fyi/results/html/rendering/the-details-element/details-display-type-001.tentative.html https://wpt.fyi/results/html/rendering/the-details-element/details-display-type-002.tentative.html https://wpt.fyi/results/html/rendering/the-details-element/details-display-type-001-ref.html https://wpt.fyi/results/html/rendering/the-details-element/details-pseudo-elements-001.tentative.html https://wpt.fyi/results/html/rendering/the-details-element/details-pseudo-elements-002.tentative.html https://wpt.fyi/results/html/rendering/the-details-element/details-pseudo-elements-003.tentative.html
  - User research: none
  - Security and Privacy self-review²: Mostly not relevant since this is not adding new capabilities but only improving the ability to combine existing capabilities.
  - GitHub repo: https://github.com/openui/open-ui/issues/744 / https://github.com/w3c/csswg-drafts/issues/9879
  - Primary contacts (and their relationship to the specification):
      - L. David Baron (@dbaron), Google Chrome
      - Greg Whitworth (@gregwhitworth), Open UI CG co-chair
      - Mason Freed (@mfreed7), Open UI GC co-chair
      - Alan Stearns (@astearns), CSS WG co-chair
      - Rossen Atanassov (@atanassov), CSS WG co-chair
  - Organization(s)/project(s) driving the specification: Google Chrome
  - Key pieces of existing multi-stakeholder (e.g. developers, implementers, civil society) support, review or discussion of this specification
  - Key pieces of multi-implementer support:
    - Chromium comments: primary advocate for feature
    - Mozilla comments: https://github.com/mozilla/standards-positions/issues/1027
    - WebKit comments: https://github.com/WebKit/standards-positions/issues/351
  - External status/issue trackers for this specification (publicly visible, e.g. Chrome Status): https://chromestatus.com/feature/5112013093339136

Further details:

  - [X] I have reviewed the TAG's [Web Platform Design Principles](https://www.w3.org/TR/design-principles/)
  - Relevant time constraints or deadlines: hoping to ship this sooner rather than later
  - The group where the work on this specification is currently being done: Mix of Open UI Community Group, CSS Working Group, and WHATWG.
  - The group where standardization of this work is intended to be done (if current group is a community group or other incubation venue): CSS Working Group and WHATWG
  - Major unresolved issues with or opposition to this specification: No major *unresolved* issues currently known.
  - This work is being funded by: Google.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/965
You are receiving this because you are subscribed to this thread.

Message ID: <w3ctag/design-reviews/issues/965@github.com>