Skip to content

Add/update Chromium data for Document API#6836

Merged
foolip merged 6 commits intomdn:masterfrom
queengooborg:api/Document-chrome
Oct 9, 2020
Merged

Add/update Chromium data for Document API#6836
foolip merged 6 commits intomdn:masterfrom
queengooborg:api/Document-chrome

Conversation

@queengooborg
Copy link
Copy Markdown
Contributor

This PR updates the Chromium data for the Document API based upon a combination of manual testing and collector results to achieve more real data for the Document API. (Note: most Opera updates have been deferred to #6835.)

Tests used: https://mdn-bcd-collector.appspot.com/tests/api/Document

@github-actions github-actions bot added the data:api Compat data for Web APIs. https://developer.mozilla.org/docs/Web/API label Oct 5, 2020
Copy link
Copy Markdown
Contributor

@foolip foolip left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I reviewed this for a bit, but it's too big, changing something like 285 things. Can you split this alphabetically or something like that into at least 3 pieces, so it's more manageable to review?

@foolip
Copy link
Copy Markdown
Contributor

foolip commented Oct 9, 2020

Thanks for trimming this, now I think it's small enough for me to review. Diving in!

Copy link
Copy Markdown
Contributor

@foolip foolip left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A few changes requested here. I'll not revert bits and land directly in this case, since I'm not certain about every suggestion.

"support": {
"chrome": {
"version_added": "43"
"version_added": "36"
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"version_added": "23"
},
{
"version_added": "≤12.1",
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"chrome": [
{
"version_added": "45"
"version_added": "37"
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

(This is api.Document.exitPointerLock.) "45" came from #1324 so this is from the wiki, but I bet a lot of "45" are actually because https://omahaproxy.appspot.com/ can't handle commits before the Blink merge into Chromium. Happy to see these errors being sorted out.

https://caniuse.com/pointerlock agrees too. We're missing version_removed for the prefixed entry, but we'll discover that when mdn-bcd-collector coverage of prefixed stuff plus our updater improves.

"chrome": {
"version_added": false
"version_added": "1",
"version_removed": true
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It was probably removed long ago, this is introducing uncertainty for what's in current Chrome. Can you either add the exact removal version or defer this change until later when it is known?

"version_added": "58"
},
{
"version_added": "32",
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The data that this is mirroring is wrong. document.onwebkitfullscreenchange was in Chrome 15 per http://mdn-bcd-collector.appspot.com/tests/api/Document/onwebkitfullscreenchange, probably earlier. Can you update the Chrome data for that, or just not mirror the incorrect data until it's fixed?

}
],
"chrome": {
"version_added": "62"
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This seems much too new. I suspect a similar situation as in #6849, can you break out this change?

},
"edge": {
"version_added": false
"version_added": "85"
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I thought Edge had shipped document.requestStorageAccess before Chrome, but maybe not. They were directly involved though: https://blogs.windows.com/msedgedev/2020/07/08/introducing-storage-access-api/

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

MS is driving the implementation in chromium: https://bugs.chromium.org/p/chromium/issues/detail?id=989663

They enabled it to be on by default in Edge before Chrome but I can’t find any publicly source that indicates which Edge version it was enabled in 😿

@foolip
Copy link
Copy Markdown
Contributor

foolip commented Oct 9, 2020

Actually, since this ends up blocking #6864 I will revert the bits I had comments on myself, and summarize needed follow-up in a comment.

- document.height/width
- document.onwebkitfullscreenchange/error
- document.onvisibilitychange
- document.queryCommandIndeterm
@foolip foolip merged commit 8dcd73f into mdn:master Oct 9, 2020
@foolip
Copy link
Copy Markdown
Contributor

foolip commented Oct 9, 2020

Alright, merged. The required followup is simply the stuff reverted in 8dcd73f:

  • document.height/width
  • document.onwebkitfullscreenchange/error
  • document.onvisibilitychange
  • document.queryCommandIndeterm

@queengooborg queengooborg deleted the api/Document-chrome branch October 9, 2020 20:29
foolip added a commit that referenced this pull request Oct 30, 2020
…ias (#6865)

This commit updates the Chromium data for various Document API
features that were initially implemented on `HTMLDocument`, first by
obtaining the version numbers via the mdn-bcd-collector project, then
separating them into sections with `partial_implementation`.  This is
a cherry-pick from #6836, applying the review suggestions from
#6836 (comment).

Co-authored-by: Philip Jägenstedt <[email protected]>
queengooborg added a commit to queengooborg/browser-compat-data that referenced this pull request Mar 2, 2022
This PR adapts the pointerlockchange and pointerlockerror event of the Document API to conform to the new events structure.

The data for Chromium was updated to adhere to the event handler data's changes in mdn#6836.  Prefixed data was left alone.
Elchi3 pushed a commit that referenced this pull request Mar 14, 2022
#15230)

This PR adapts the pointerlockchange and pointerlockerror event of the Document API to conform to the new events structure.

The data for Chromium was updated to adhere to the event handler data's changes in #6836.  Prefixed data was left alone.
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 this pull request may close these issues.

4 participants