Move <base> out of drafts
#1341
Conversation
github-actions
bot
added
the
feature definition
| - api.HTMLBaseElement.target | ||
| - html.elements.base | ||
| - html.elements.base.href | ||
| - html.elements.base.href.forbid_data_javascript_urls |
There was a problem hiding this comment.
Seeing this in a burndown caused me to include it here.
This is one of many, many behavioral features in BCD that's a bit backwards: the old behavior ought to be a deprecated "feature" that gets removed in a couple of years after everything has settled. This is never something you'd "use" about the feature—rather, it's something that defines what the feature isn't.
For completeness, I've included it, but I'm sorely tempted to create an issue in BCD to start tracking all of these backwards features, so we can eventually flip them around and purge them.
That said, this specific one is new, so I could be persuaded to go flip this one now.
There was a problem hiding this comment.
Should we just remove behavioral features from all of our burndown tracking? They never have their own MDN pages, so what is anyone ever going to do with the statuses?
There was a problem hiding this comment.
Meh, ignore my suggestion. Sometimes they'll be useful in compute_from I'm sure, and providing a status for them is harmless.
There was a problem hiding this comment.
They do get their own pages on caniuse though: https://caniuse.com/mdn-html_elements_base_href_forbid_data_javascript_urls
foolip
left a comment
foolip
left a comment
There was a problem hiding this comment.
There's a tiny mismatch in early Safari data about <base> vs HTMLBaseElement that I'm pretty sure is wrong in BCD, but it's inconsequential.
2 participants
No description provided.