Closed
Bug 1397981
Opened 7 years ago
Closed 7 years ago
Interactive content inside a button element is inactive in Firefox per spec
Categories
(Core :: DOM: Core & HTML, defect, P2)
Tracking
()
RESOLVED
DUPLICATE
of bug 1089326
Tracking | Status | |
---|---|---|
firefox57 | --- | affected |
People
(Reporter: karlcow, Unassigned)
References
Details
(Whiteboard: [webcompat])
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.
Reporter | ||
Comment 1•7 years ago
|
||
Adding some examples with the same issue.
Rick that might be something interesting for you too.
Flags: webcompat?
See Also: → https://bugzilla.mozilla.org/show_bug.cgi?id=1089326,
https://webcompat.com/issues/9726,
https://webcompat.com/issues/3575,
https://webcompat.com/issues/4909,
https://webcompat.com/issues/9196
Whiteboard: [webcompat]
Comment 2•7 years ago
|
||
Hi Ben, please help this.
According to the webcompat issue reports, it's an old issue, reporting back to ff51.
Priority: -- → P2
Updated•7 years ago
|
Flags: needinfo?(btian)
Comment 3•7 years ago
|
||
Will check if any related issue of HTML spec already exists.
Comment 4•7 years ago
|
||
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.
Flags: needinfo?(dbolter)
Comment 5•7 years ago
|
||
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.
Flags: needinfo?(dbolter)
Updated•7 years ago
|
See Also: → https://webcompat.com/issues/13505
Reporter | ||
Updated•7 years ago
|
See Also: → https://webcompat.com/issues/14565
Reporter | ||
Comment 6•7 years ago
|
||
Maybe it would be worth to open a new bug in Chromium, WebKit?
Or Anne do you think we should change the spec here?
Flags: needinfo?(annevk)
Reporter | ||
Updated•7 years ago
|
See Also: → https://webcompat.com/issues/5028
Comment 7•7 years ago
|
||
How is this different from bug 1089326?
Flags: needinfo?(annevk) → needinfo?(miket)
Updated•7 years ago
|
Flags: needinfo?(ben.tian)
Comment 8•7 years ago
|
||
(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.
Flags: needinfo?(miket)
Updated•7 years ago
|
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•