summary element definition does not reflect implementations

[stevefaulkner]

In all implementations: blink/webkit/firefox the summary element is an interactive element. It receives focus and is operated to open/close the details element. It is also exposed as a control via acc APIs in all implementations.

Suggest the spec should be updated to reflect this.

[annevk]

Yeah, we should probably define activation behavior for it.

[stevefaulkner]

suggest the following also need to be updated:

Categories:
None.
Contexts in which this element can be used:
As the first child of a details element.
Content model:
Either: phrasing content.
Or: one element of heading content.

https://html.spec.whatwg.org/multipage/forms.html#the-summary-element

and https://html.spec.whatwg.org/multipage/forms.html#the-details-element

[domenic]

@stevefaulkner why would those be updated? They're unrelated to the activation behavior.

[stevefaulkner]

@domenic summary is a focusable interactive element?

as per https://html.spec.whatwg.org/multipage/dom.html#interactive-content-2

[domenic]

Sure, in some browsers it does have the tabindex focus flag set. Why does that impact the categories or content model?

[stevefaulkner]

because its interactive content "Interactive content is content that is specifically intended for user interaction."

[domenic]

I see, we need to update the definition of the interactive content category to include it (when it meets the requirements)

[stevefaulkner]

Also details is listed as interactive content, when it doesn't appear to be.

[domenic]

Ah yeah OK, so summary should not be; details covers that case. This is especially important, e.g., for details elements without a summary.

(Remember interactive content is a content category for authoring requirements, separate from the activation behavior which defines the processing model.)

Another good example of this is how video (with controls) is interactive content, even though the element itself is not interactive, the controls inside of it are. Similarly details is interactive content, even though actually it's the UA-generated widget whose contents are drawn from the summary element that are interactive, not the whole details.

[stevefaulkner]

ok

[zcorpan]

Hmm. I think there's a piece missing in the content models. The summary element should disallow interactive descendants. Filed #2272