1397981 - Interactive content inside a button element is inactive in Firefox per spec

Status: RESOLVED DUPLICATE of bug 1089326

(Core :: DOM: Core & HTML, defect, P2)

Description

[Karl Dubost💡 :karlcow]

In https://webcompat.com/issues/9726

Mike Taylor found for the glitch.com issue:

> HTML specification [1] for button element says:
> [1]: https://html.spec.whatwg.org/multipage/form-elements.html#the-button-element
> 
> > Content model:
> >    Phrasing content, but there must be no interactive content descendant.
> 
> And <a> is considered interactive content if it has an href present: 
> https://html.spec.whatwg.org/multipage/dom.html#interactive-content-2


Markup Example:

<button>
   <a href="https://w3.org/">W3C</a>
</button>

Edge, Chrome and Safari are working (against the spec). 
Firefox and Old Opera Presto don't (per spec).

In the past I duplicated this type of issues against Bug 1089326, but Mike says it's different. So let's re qualify them a bit.

Comment 1

[Karl Dubost💡 :karlcow]

Adding some examples with the same issue.


Rick that might be something interesting for you too.

Comment 2

[Hsin-Yi Tsai (she/her) [:hsinyi]]

Hi Ben, please help this. 

According to the webcompat issue reports, it's an old issue, reporting back to ff51.

Comment 3

[Ben Tian (inactive)]

Will check if any related issue of HTML spec already exists.

Comment 4

[Mike Taylor [:miketaylr]]

Note, glitch updated their site. Also, anchors inside of buttons appear to be invisible to AT (at least VoiceOver in Safari). Not sure if a11y has input here.

Comment 5

[David Bolter [:davidb] (NeedInfo me for attention)]

We want to provide the same access as a sighted user. If this doesn't work for sighted users it doesn't need to work for AT. Let me know if that changes.

Comment 6

[Karl Dubost💡 :karlcow]

Maybe it would be worth to open a new bug in Chromium, WebKit?

Or Anne do you think we should change the spec here?

Comment 7

[Anne (:annevk)]

How is this different from bug 1089326?

Comment 8

[Mike Taylor [:miketaylr]]

(In reply to Anne (:annevk) from comment #7)
> How is this different from bug 1089326?

Oh, I thought that was specifically about event.target when I filed this (even though I've apparently commented). I'll move over the deps and fix the title.