Closed Bug 1856374 Opened 1 year ago Closed 1 year ago

Allow changing `display` of `<details>` elements

Categories

(Core :: Layout, defect, P3)

Desktop
All
defect

Tracking

()

RESOLVED FIXED
120 Branch
Tracking Status
firefox120 --- fixed

People

(Reporter: Gijs, Assigned: emilio)

References

Details

Attachments

(1 file)

I noticed that I couldn't get flexbox to work for a <details>/<summary> pair. Emilio pointed to the spec which says:

The details element is expected to render as a block box.

which ends up meaning that (cross-browser) you cannot change its display value to flex. Emilio suggested this may change in the future, and we could experiment with it behind a pref.

Flags: needinfo?(emilio)

David, this is the "<details> is always a block" bit that I mentioned when you brought up details styling. Do you know if there's an issue on the HTML spec to remove that requirement or if that's part of your work for <details> improvements?

Flags: needinfo?(dbaron)

This is probably something we want to move towards, so it doesn't hurt
adding a pref to allow people to experiment with it.

Assignee: nobody → emilio
Status: NEW → ASSIGNED
Flags: needinfo?(emilio)

I'm not aware of an issue against the HTML spec on this.

I am interested in working on fixing this, as discussed in the CSS WG meeting in July. I've prototyped this change and some other changes in Chromium in https://crbug.com/1469418 , but with the intent of experimenting with what I prototyped and likely making major changes. I got a bunch of feedback from Bramus who tried to use the prototype to build a bunch of things with it, and I'm part of the way done going through that feedback. Once I do that, I need to (possibly not in this order) write some major updates to https://github.com/dbaron/details-styling, probably try to get another round of feedback from Bramus and hopefully build a few demos, and start making some more concrete proposals for what to change in some combination of the Open UI CG / the CSS WG / the HTML spec. I'm hoping to get back to working on that sometime this month (but I've spent the past month mostly doing two other things, one of which is <details name>).

Flags: needinfo?(dbaron)
Severity: -- → S3
Priority: -- → P3
Pushed by ealvarez@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/4416f2eba0ce Add a pref to stop forcing details elements to be blocks. r=TYLin
Created web-platform-tests PR https://github.com/web-platform-tests/wpt/pull/42367 for changes under testing/web-platform/tests
Status: ASSIGNED → RESOLVED
Closed: 1 year ago
Resolution: --- → FIXED
Target Milestone: --- → 120 Branch
Upstream PR merged by moz-wptsync-bot
Duplicate of this bug: 1269642
Duplicate of this bug: 1245430
Duplicate of this bug: 1245431
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: