Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

DocumentOrShadowRoot APIs are marked as too new #3504

Closed
saschanaz opened this issue Feb 22, 2019 · 3 comments · Fixed by #9045
Closed

DocumentOrShadowRoot APIs are marked as too new #3504

saschanaz opened this issue Feb 22, 2019 · 3 comments · Fixed by #9045
Labels
data:api 🐇 Compat data for Web APIs. https://developer.mozilla.org/docs/Web/API

Comments

@saschanaz
Copy link
Contributor

Nearly everything there is marked as added in Chrome 53/Firefox 63, but those versions are really the ones that added ShadowRoot support. Many APIs there had been existed in Document before DocumentOrShadowRoot so we have to properly represent them.

@ddbeck ddbeck added the data:api 🐇 Compat data for Web APIs. https://developer.mozilla.org/docs/Web/API label Feb 22, 2019
@foolip
Copy link
Collaborator

foolip commented Mar 16, 2019

Related: #472

@queengooborg
Copy link
Collaborator

I believe that we can resolve this by turning both Chrome and Firefox into arrays of compatibility statements. Specifically, one with the version that was added, with a partial implementation flag and a note stating "Only available in the Document API."

@foolip
Copy link
Collaborator

foolip commented Sep 1, 2019

We could do that, but that wouldn't be machine readable. I think spitting the entries would be better.

@Elchi3 FYI, here's a concrete case of mixin troubles.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
data:api 🐇 Compat data for Web APIs. https://developer.mozilla.org/docs/Web/API
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants