Open edoardocavazza opened 2 months ago
Autonomous custom elements should be treated as non-interactive elements.
Do you have some link that we can use as a source of truth?
I admit that the statement may have been a bit strong, but I believe it to be fundamentally accurate.
Autonomous custom elements, as described here Using custom elements, directly extend the HTMLElement
class, and thus, they do not possess any inherent interactivity.
On the other hand, customized built-in elements extend classes of interactive elements like <button>
, <a>
, etc., which is a different case.
The reason I'm asking is because this needs to be documented, in case this is a valid bug. So a W3C link that explains this is beneficial for us developers and end users
Environment information
Rule name
noInteractiveElementToNoninteractiveRole
Playground link
https://biomejs.dev/playground/?code=ZgB1AG4AYwB0AGkAbwBuACAAcgBlAG4AZABlAHIAQwB1AHMAdABvAG0ARQBsAGUAbQBlAG4AdABXAGkAdABoAFIAbwBsAGUAKAApACAAewAKACAAIAByAGUAdAB1AHIAbgAgADwAeAAtAGUAbABlAG0AZQBuAHQACgAgACAAIAAgACAAcgBvAGwAZQA9ACIAZwByAG8AdQBwACIAIAAgACAAIAAgACAACgAgACAAIAAvAD4ACgB9AA%3D%3D
Expected result
Autonomous custom elements should be treated as non-interactive elements.
Code of Conduct