Many areas of HTML prohibit nesting interactive content, for example the content model of the <a> element is:
Transparent, but there must be no interactive content descendant, a element descendant, or descendant with the tabindex attribute specified.
It's common to have content within maps overlapping. This is probably impossible to avoid with multiple layer sources, and even a single layer source can produce nested interactive elements (<map-a>).
I think it's important that this proposal talks about this. Supposedly in Key Scenarios.
Nested/overlapping interactive content is problematic for users with a pointing device or touch-enabled devices. One way to solve interacting with nested and/or overlapping content is a Feature Index.
Many areas of HTML prohibit nesting interactive content, for example the content model of the
<a>element is:It's common to have content within maps overlapping. This is probably impossible to avoid with multiple layer sources, and even a single layer source can produce nested interactive elements (
<map-a>).I think it's important that this proposal talks about this. Supposedly in Key Scenarios.
Nested/overlapping interactive content is problematic for users with a pointing device or touch-enabled devices. One way to solve interacting with nested and/or overlapping content is a Feature Index.