You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This issue in the MDN Web Docs mdn/content#28446 mentions that Chrome browsers use generic as the implicit role while Firefox uses summary as the implicit role.
It might be worth mentioning in the NOTE for the summary element the behavior of a few of the most popular browsers.
P.S.
My apologies if user-agent/browser-specific details are not allowed in the official specs. I am new to this.
Thank you
The text was updated successfully, but these errors were encountered:
thanks for the heads up, i'm going to respond in more detail over on the MDN issue. But yeh, this sort of information doesn't belong here. This spec doesnt even actually normatively define the role for HTML elements. That happens in the HTML AAM spec (linked to for each element in this spec) - and there too that's for how the browser engines are supposed to map the element. that spec would not get into the individual browser support, as that's not the point of the spec.
This issue in the MDN Web Docs mdn/content#28446 mentions that Chrome browsers use
generic
as the implicit role while Firefox usessummary
as the implicit role.It might be worth mentioning in the NOTE for the summary element the behavior of a few of the most popular browsers.
P.S.
My apologies if user-agent/browser-specific details are not allowed in the official specs. I am new to this.
Thank you
The text was updated successfully, but these errors were encountered: