Queen Vinyl Da.i'gyu-Kazotetsu

I moved this issue over to mdn/content so that the page can be created, but after looking deeper into this, I actually think that this entire set of data should...

On the BCD side, we typically say that a feature that has been in one browser for a long period of time should be considered non-experimental, but what do you...

> I used dialed down version the [test-status.ts#checkExperimental()](https://github.com/mdn/browser-compat-data/blob/75b2c77d0623c54b965b4598030b80269f4f2c2c/test/linter/test-status.ts#L18) to find these. If we consider flags, prefixes, and alternative names then there will be ~316 files modified in the entire repo....

Experimental set to true sounds good to me! I've opened up https://github.com/mdn/browser-compat-data/pull/17367 to add v16.14.0 to the browser data, and will merge that promptly so this PR passes!

In a case like that, I'd say that we should do the following: ```json [ { "version_added": "17.5.0" }, { "version_added": "16.15.0", "version_removed": "17.0.0" }, { "version_added": "17.0.0", "version_removed": "17.5.0",...

Yeah, it's an ugly solution, but I feel it is a necessary one due to how NodeJS' release cycle works. On the plus side, doing this allows us to better...

I have proposed a solution already, actually -- see https://github.com/mdn/browser-compat-data/pull/17366#issuecomment-1214894126!

> Can you describe the testing done, with links to the tests where possible? The test code is actually in the issue description!

Here's an updated example that shows the attribute working on other elements: https://codepen.io/queengooborg/pen/QWrYaXg

+1 for getting this functionality added back in. Just like optional routing parameters, this was such a useful (and critical feature), and it's not clear why this functionality was removed...we're...