search

mozilla / standards-positions

https://mozilla.github.io/standards-positions/
Mozilla Public License 2.0
639 stars 69 forks source link

Exclusive accordions with <details name=""> #831

Closed dbaron closed 1 year ago

dbaron commented 1 year ago

Request for Mozilla Position on an Emerging Web Specification

zcorpan commented 1 year ago

I like the direction here and it aligns with our vision for the web with more declarative solutions that are accessible by default (as opposed to implementing a widget like this with JS + ARIA).

Suggest positive.

zcorpan commented 1 year ago

No dashboard entry since it's more of an incremental improvement for details.

smaug---- commented 1 year ago

But the current setup requires JS. Before implementing this having reasonable behavior during page load is rather important. In other words, I'm not sold on the proposed solution here https://open-ui.org/components/accordion.explainer/#interaction-with-open-attribute

dbaron commented 1 year ago

What is it that requires JS?

Would it help to clarify things if we made it an explicit document conformance requirement not to have more than one <details> element in a single name-group that has an open attribute?

smaug---- commented 1 year ago

The proposed solution explicitly talks about setAttribute or open attributes, in addition to user interaction. So to set initial state, one needs to use JS.

dbaron commented 1 year ago

Setting initial state does not require JS. It can be done by using an open attribute in the markup. I would describe is as an authoring error to use an open attribute in the markup on more than one element in a group.

MBeggiato commented 3 months ago

Is there any progress on this issue? Firefox is the last browser to not support the nameattribute.

zcorpan commented 3 months ago

This is not the right place to follow implementation progress in Gecko. https://bugzilla.mozilla.org/show_bug.cgi?id=1856460 is.