Feature request: copyable BCD keys

[ddbeck]

Right now, features are shown with a pretty formatting, as in api ➞ HTMLBaseElement ➞ href ➞ forbid_special_characters. This is fine for reading.

But sometimes I see a key or group of keys that inspires me to author a feature in web-features. I'd like to copy those items into a web-features YAML file, or use a script to find the data in BCD. In those cases, I'd prefer to have the dot notation conventional to BCD and web-features, such as api.HTMLBaseElement.href.forbid_special_characters.

Thanks for considering this!

[bkardell]

So they'd be like this, effectively?

[bkardell]

Just to clarify - I posted this mainly because it was easy to querySelector/replace and then have a 1:1 to say "so these are the values you'd want copyable" rather than "this is how we'd display them"... I'm not sure how I feel about the later, but ... yeah, what do you think?

[ddbeck]

Yeah, I should distinguish a bit here: it'd be nice if I could easily copy text in the form css.properties.position-try-fallbacks.none, regardless of the presentation. I don't have an opinion on how it ought to look.

[bkardell]

Ok, we're seriously considering doing this - but we're thinking it probably would be confusing to most people, so we've been discussing ways to let some people uncover more -- like maybe let you give a hash argument on the URL or something to indicate you actually want that. Anyway, it dawned on me that you could also just make a bookmarklet, something like

javascript:(function()%7Bdocument.querySelectorAll('li').forEach(it%20%3D%3E%20%7B%0A%20%20%20%20it.innerHTML%20%3D%20it.innerHTML.replaceAll('%20%E2%9E%9E%20'%2C%20'.')%0A%7D)%7D)()%3B

[bkardell]

After some further discussion, @meyerweb and I believe that perhaps a bookmark solution, works pretty well for this and won't confuse anyone, so closing this as wontfix (for now) and providing the bookmark solution (above) that you can save

[ddbeck]

Thank you!