HTML: <object usemap> is removed #27184
Open
+4
−14
Conversation
wpt-pr-bot
requested review from
domenic,
foolip,
jdm,
jgraham,
tkent-google and
zqzhang
|
(You could imagine more cases by the way such as what happens when the |
|
Ping @mfreed7 on whether you're interested in this minor |
|
Yes, I'm definitely interested in this cleanup. We have no use counters, but this seems rather safe. In Chromium, this is made interactive here, but I don't see any other behavioral changes to actually do anything other than that. Happy to remove that. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Tests for whatwg/html#6283.
So the curious case here is
html/semantics/forms/the-label-element/clicking-interactive-content.htmlwhere browsers fail for<object>but not<object usemap>. If I add<span>or<div>I get the same results (only the last of the three tests fails) so I suspect that all browsers do have some logic to consider<object usemap>interactive? Despite Chrome and Safari not supporting<object usemap>otherwise.