Add complete BCD for Window Management API #20600
Conversation
github-actions
bot
added
data:http 🚠
api/Permissions.json
Outdated
| @@ -891,4 +927,4 @@ | |||
| } | |||
| } | |||
| } | |||
| } | |||
| } | |||
There was a problem hiding this comment.
I saw this change in your PRs and ignored it but then Vinyl opened #20560 so I think we do care about this. Please fix your editor config and don't change this from now on :)
There was a problem hiding this comment.
Oh wow, I honestly never knew this was a thing to be concerned about! I have removed the odd newline here and there because I thought they were unnecessary.
I've updated my config so VSCode adds newlines to the end of all files on save, and added the missing ones into this PR. Sorted.
| @@ -34,7 +34,7 @@ | |||
| }, | |||
| "availLeft": { | |||
| "__compat": { | |||
| "spec_url": "https://w3c.github.io/window-management/#ref-for-dom-screendetailed-availleft", | |||
There was a problem hiding this comment.
Why is this change necessary?
@sideshowbarker has opinions about where to link in the specs. I think it has to do with where the MDN ribbon appears.
There was a problem hiding this comment.
The practice followed by the majority of the existing spec URLs is to use the URL for the developer part of the spec, if any. In this case, that’s https://w3c.github.io/window-management/#ref-for-dom-screendetailed-availleft
And yeah the effect of that as far as the rendering of the published specs goes is that it causes the MDN annotation in the spec to be shown next the developer part of the spec (rather than the implementor part).
There was a problem hiding this comment.
OK, makes sense. I've reverted those changes, and added some other developer spec URLs
* Add complete BCD for Window Management API * Add missing newlines * Update spec URLs to developer defs where possible * Add MDN URLs for ScreenDetailed and ScreenDetails
Summary
The Window Management API was implemented in Chrome 100 (see ChromeStatus entry); this PR provides complete BCD for it (some was available already).
Test results and supporting details
Related issues