Browser-compat-data: All remaining Web APIs without PRs

Created on 13 Jul 2018 · 29Comments · Source: mdn/browser-compat-data

Here are all the remaining Web APIs without PRs, plus their subfeatures (Spreadsheet Source):

[x] [Web/API/BluetoothDevice](https://developer.mozilla.org/en-US/docs/Web/API/BluetoothDevice) (#2611)
- Web/API/BluetoothDevice/adData
- Web/API/BluetoothDevice/connectGATT
- Web/API/BluetoothDevice/deviceClass
- Web/API/BluetoothDevice/gatt
- Web/API/BluetoothDevice/gattServer
- Web/API/BluetoothDevice/id
- Web/API/BluetoothDevice/name
- Web/API/BluetoothDevice/productID
- Web/API/BluetoothDevice/productVersion
- Web/API/BluetoothDevice/uuids
- Web/API/BluetoothDevice/vendorID
- Web/API/BluetoothDevice/vendorIDSource
[x] [Web/API/Coordinates](https://developer.mozilla.org/docs/Web/API/Coordinates) (#2587)
- Web/API/Coordinates/accuracy
- Web/API/Coordinates/altitude
- Web/API/Coordinates/altitudeAccuracy
- Web/API/Coordinates/heading
- Web/API/Coordinates/latitude
- Web/API/Coordinates/longitude
- Web/API/Coordinates/speed
[x] [Web/API/Element](https://developer.mozilla.org/en-US/docs/Web/API/Element)
- See #2494 for the full list of Element subfeatures.
[x] [Web/API/File/webkitRelativePath](https://developer.mozilla.org/en-US/docs/Web/API/File/webkitRelativePath) (#2791)
[x] [Web/API/FileException](https://developer.mozilla.org/en-US/docs/Web/API/FileException) (#2790)
[x] [Web/API/HTMLIFrameElement/setNfcFocus](https://developer.mozilla.org/en-US/docs/Web/API/HTMLIFrameElement/setNfcFocus) (#2877)
[x] [Web/API/HTMLInputElement](https://developer.mozilla.org/en-US/docs/Web/API/HTMLInputElement) (#2881 / #2884)
- Web/API/HTMLInputElement/labels
- Web/API/HTMLInputElement/setSelectionRange
- Web/API/HTMLInputElement/webkitdirectory
[x] [Web/API/IDBFactory/open-obsolete](https://developer.mozilla.org/en-US/docs/Web/API/IDBFactory/open-obsolete) (redirected)
[x] [Web/API/MediaDevices](https://developer.mozilla.org/en-US/docs/Web/API/MediaDevices) (#2472)
- Web/API/MediaDevices/enumerateDevices
- Web/API/MediaDevices/getSupportedConstraints
- Web/API/MediaDevices/getUserMedia
- Web/API/MediaDevices/ondevicechange
[x] [Web/API/NamedNodeMap](https://developer.mozilla.org/en-US/docs/Web/API/NamedNodeMap) (#1682)
- Web/API/NamedNodeMap/length
- Web/API/NamedNodeMap/getNamedItem
- Web/API/NamedNodeMap/setNamedItem
- Web/API/NamedNodeMap/removeNamedItem
- Web/API/NamedNodeMap/item
- Web/API/NamedNodeMap/getNamedItemNS
- Web/API/NamedNodeMap/setNamedItemNS
- Web/API/NamedNodeMap/removeNamedItemNS
[x] [Web/API/Navigator/maxTouchPoints](https://developer.mozilla.org/en-US/docs/Web/API/Navigator/maxTouchPoints) (#2508)
[x] [Web/API/ReadableByteStreamController](https://developer.mozilla.org/en-US/docs/Web/API/ReadableByteStreamController) (#2768)
- Web/API/ReadableByteStreamController/ReadableByteStreamController
- Web/API/ReadableByteStreamController/byobRequest
- Web/API/ReadableByteStreamController/desiredSize
- Web/API/ReadableByteStreamController/close
- Web/API/ReadableByteStreamController/enqueue
- Web/API/ReadableByteStreamController/error
[x] [Web/API/ReadableStreamBYOBReader](https://developer.mozilla.org/en-US/docs/Web/API/ReadableStreamBYOBReader) (#2767)
- Web/API/ReadableStreamBYOBReader/ReadableStreamBYOBReader
- Web/API/ReadableStreamBYOBReader/closed
- Web/API/ReadableStreamBYOBReader/cancel
- Web/API/ReadableStreamBYOBReader/read
- Web/API/ReadableStreamBYOBReader/releaseLock
[x] [Web/API/ReadableStreamDefaultController](https://developer.mozilla.org/en-US/docs/Web/API/ReadableStreamDefaultController) (#2667)
- Web/API/ReadableStreamDefaultController/ReadableStreamDefaultController
- Web/API/ReadableStreamDefaultController/desiredSize
- Web/API/ReadableStreamDefaultController/close
- Web/API/ReadableStreamDefaultController/enqueue
- Web/API/ReadableStreamDefaultController/error
[x] [Web/API/ReadableStreamDefaultReader](https://developer.mozilla.org/en-US/docs/Web/API/ReadableStreamDefaultReader) (#2663)
- Web/API/ReadableStreamDefaultReader/ReadableStreamDefaultReader
- Web/API/ReadableStreamDefaultReader/closed
- Web/API/ReadableStreamDefaultReader/cancel
- Web/API/ReadableStreamDefaultReader/read
- Web/API/ReadableStreamDefaultReader/releaseLock
[x] [Web/API/RTCRtpTransceiverDirection](https://developer.mozilla.org/en-US/docs/Web/API/RTCRtpTransceiverDirection) (#2608)
[x] [Web/API/RTCRtpTransceiverInit](https://developer.mozilla.org/en-US/docs/Web/API/RTCRtpTransceiverInit) (#2610)
- Web/API/RTCRtpTransceiverInit/direction
- Web/API/RTCRtpTransceiverInit/sendEncodings
- Web/API/RTCRtpTransceiverInit/streams
[x] [Web/API/ScriptProcessorNode](https://developer.mozilla.org/en-US/docs/Web/API/ScriptProcessorNode) (#2665)
- Web/API/ScriptProcessorNode/bufferSize
- Web/API/ScriptProcessorNode/onaudioprocess
[x] [Web/API/SVGFEColorMatrixElement](https://developer.mozilla.org/en-US/docs/Web/API/SVGFEColorMatrixElement) (#2607)
[x] [Web/API/WritableStreamDefaultController](https://developer.mozilla.org/en-US/docs/Web/API/WritableStreamDefaultController) (#2664)
- Web/API/WritableStreamDefaultController/WritableStreamDefaultController
- Web/API/WritableStreamDefaultController/error
[x] [Web/API/XDomainRequest](https://developer.mozilla.org/en-US/docs/Web/API/XDomainRequest) (#2507)
- Web/API/XDomainRequest/abort
- Web/API/XDomainRequest/onerror
- Web/API/XDomainRequest/onload
- Web/API/XDomainRequest/onprogress
- Web/API/XDomainRequest/ontimeout
- Web/API/XDomainRequest/open
- Web/API/XDomainRequest/responseText
- Web/API/XDomainRequest/send
- Web/API/XDomainRequest/timeout

Getting very close to the end! :D There are also a few dozen CSS features to move over, as well as a small handful of SVG and HTML features.

data help wanted

Source

connorshea

❤2 👍1

Most helpful comment

(In reply to @connorshea from https://github.com/mdn/browser-compat-data/issues/2467#issuecomment-425469400)

@ExE-Boss would the better-errors package have made those error messages easier to understand in this case? #2143

Yes, it would. #2338 makes it so that schema validation errors are highlighted with a red underline in the log (see here for an example).

ExE-Boss on 28 Sep 2018

👍2

All 29 comments

There's also Web/API/PermissionStatus/status, which was excluded from #2284 because the subfeature was deprecated. Not sure if we should include that.

connorshea on 13 Jul 2018

(In reply to @connorshea from https://github.com/mdn/browser-compat-data/issues/2467#issuecomment-404954935)

There's also Web/API/PermissionStatus/status, which was excluded from #2284 because the subfeature was deprecated. Not sure if we should include that.

Did any browser ship a working implementation at any point before it was deprecated?

If yes, then we should add it.

P.S.: You can create nested task lists: (click to expand)

- [ ] Item 1
    - [x] Item 1 Sub-item 1
    - [ ] Item 1 Sub-item 2
- [x] Item 2
    - [x] Item 2 Sub-item 1
    - [x] Item 2 Sub-item 2
- [ ] Item 3
    - [ ] Item 3 Sub-item 1
    - [x] Item 3 Sub-item 2

[ ] Item 1
- [x] Item 1 Sub-item 1
- [ ] Item 1 Sub-item 2
[x] Item 2
- [x] Item 2 Sub-item 1
- [x] Item 2 Sub-item 2
[ ] Item 3
- [ ] Item 3 Sub-item 1
- [x] Item 3 Sub-item 2

ExE-Boss on 14 Jul 2018

I didn’t add checkboxes to each subfeature since I figured most of the features would be done with their subfeatures all at once.

And yeah I believe a browser implemented the status property previously, so we should add it.

connorshea on 14 Jul 2018

Element has 77 subfeatures according to the MDN sidebar (34 properties + 43 methods), though some of them are inherited from other APIs. 🤔#2316 completes the data for some of them, but not all of them.

EDIT: I've opened #2494 to track all the Element subfeatures.

connorshea on 18 Jul 2018

Worth noting that Entity and EntityReference are obsolete and don't seem to have any browser support. We should probably not migrate them so I've removed them from the list.

connorshea on 20 Jul 2018

👍1

Removed window.URL and window.StaticRange because the pages were deleted.

connorshea on 7 Aug 2018

I've opened PRs for RTCRtpTransceiverInit, RTCRtpTransceiverDirection, and SVGFEColorMatrixElement.

connorshea on 14 Aug 2018

👍2

I got #2611 merged, which completed the Web Bluetooth API in this repository.

ExE-Boss on 15 Aug 2018

🎉1

@ExE-Boss what does that mean for BluetoothDevice?

EDIT: It was completed in #2611, I thought it wasn't included last time I checked.

connorshea on 15 Aug 2018

I've found a few more:

Elchi3 on 24 Aug 2018

👍2

Opened a PR for DOMQuad: #2659
Opened a PR for EventTarget.attachEvent(), EventTarget.detachEvent(), and EventTarget.fireEvent(): #2660
Opened a PR for the CompositionEvent constructor: #2661
I was going to do NetworkInformation/ontypechange but the browser compat table is weird (e.g. Chrome is unsupported but Chrome for Android is supported?), the article also hasn't been updated in over three years.

connorshea on 24 Aug 2018

@Elchi3 Some notes on those pages:

DOMImplementationRegistry has no browser support based on the table, the article hasn't been updated in 3 years, and the API is marked obsolete. Unless we can find something suggesting that a browser has implemented it, should we delete the article?
Ditto for DOMImplementationSource?
I think Connection.onchange should be redirected to NetworkInformation.onchange, because the main Connection API already redirects to NetworkInformation, and the spec only mentions NetworkInformation.onchange, nothing about a Connection.onchange.
iconURL doesn't seem to be a property of Credential, only a property of CredentialUserData, FederatedCredentialInit, and PasswordCredentialData. See the sections where the term iconURL is defined in the spec. I think the article should maybe be deleted?

connorshea on 24 Aug 2018

HTMLHyperlinkElementUtils/searchParams is a really weird article and the spec doesn't seem to have anything about searchParams anymore.
Notification.sticky doesn't seem to have been implemented in any browser and is no longer in the spec.
The Notification constructor table has a bunch of extra subfeatures that I think are repetitive of the parent article, so we can probably just remove those and only have compat data for the constructor?
OfflineAudioContext/startRendering (promise) should probably be merged into OfflineAudioContext/startRendering, I would assume? The compat table for the latter page already tracks the promise-based version.
RTCPeerConnection/currentRemoteDescription seems like it should be easy enough to transfer to the new format. (Opened #2662)
HTMLInputElement/webkitEntries scares me because the entire HTMLInputElement API scares me :D

connorshea on 24 Aug 2018

Opened a few more PRs:

ReadableStreamDefaultReader #2663
WritableStreamDefaultController #2664
ScriptProcessorNode #2665
ReadableStreamDefaultController #2667

connorshea on 24 Aug 2018

Thanks for your PRs! Really helpful to finish this. :+1:

I was going to do NetworkInformation/ontypechange but the browser compat table is weird (e.g. Chrome is unsupported but Chrome for Android is supported?), the article also hasn't been updated in over three years.

This can make sense as network information is much more interesting on mobile devices often enough.

DOMImplementationRegistry has no browser support based on the table, the article hasn't been updated in 3 years, and the API is marked obsolete. Unless we can find something suggesting that a browser has implemented it, should we delete the article?

Deleted.

Ditto for DOMImplementationSource?

Deleted.

I think Connection.onchange should be redirected to NetworkInformation.onchange, because the main Connection API already redirects to NetworkInformation, and the spec only mentions NetworkInformation.onchange, nothing about a Connection.onchange.

Redirected.

iconURL doesn't seem to be a property of Credential, only a property of CredentialUserData, FederatedCredentialInit, and PasswordCredentialData. See the sections where the term iconURL is defined in the spec. I think the article should maybe be deleted?

Deleted.

HTMLHyperlinkElementUtils/searchParams is a really weird article and the spec doesn't seem to have anything about searchParams anymore.

Deleted.

Notification.sticky doesn't seem to have been implemented in any browser and is no longer in the spec.

Deleted.

The Notification constructor table has a bunch of extra subfeatures that I think are repetitive of the parent article, so we can probably just remove those and only have compat data for the constructor?

Yes, I think just the constructor data would be fine.

OfflineAudioContext/startRendering (promise) should probably be merged into OfflineAudioContext/startRendering, I would assume? The compat table for the latter page already tracks the promise-based version.

Yes, we should merge these. No compat data updates needed then. I will need a closer look if we want to move something over to the main article.

HTMLInputElement/webkitEntries scares me because the entire HTMLInputElement API scares me :D

Elchi3 on 26 Aug 2018

So that leaves us with this:

[x] https://developer.mozilla.org/en-US/docs/Web/API/CompositionEvent/CompositionEvent (#2661)
[x] https://developer.mozilla.org/en-US/docs/Web/API/Connection/onchange (redirected)
[x] https://developer.mozilla.org/en-US/docs/Web/API/Credential/iconURL (deleted)
[x] https://developer.mozilla.org/en-US/docs/Web/API/DOMImplementationRegistry (deleted)
[x] https://developer.mozilla.org/en-US/docs/Web/API/DOMQuad (#2659)
[x] https://developer.mozilla.org/en-US/docs/Web/API/EventTarget/attachevent (#2660, article will be merged into another EventTarget subfeature)
[x] https://developer.mozilla.org/en-US/docs/Web/API/EventTarget/fireEvent (#2660, article will be merged into another EventTarget subfeature)
[x] https://developer.mozilla.org/en-US/docs/Web/API/HTMLHyperlinkElementUtils/searchParams (deleted)
[ ] https://developer.mozilla.org/en-US/docs/Web/API/HTMLInputElement/webkitEntries
[ ] https://developer.mozilla.org/en-US/docs/Web/API/NetworkInformation/ontypechange
[x] https://developer.mozilla.org/en-US/docs/Web/API/notification/Notification (constructor needs to be added to the BCD, can ignore subfeatures of constructor) (#2679)
[x] https://developer.mozilla.org/en-US/docs/Web/API/Notification/sticky (deleted)
[x] https://developer.mozilla.org/en-US/docs/Web/API/OfflineAudioContext/startRendering(promise) (will be merged)
[x] https://developer.mozilla.org/en-US/docs/Web/API/RTCPeerConnection/currentRemoteDescription (#2662)

connorshea on 27 Aug 2018

Two more:

Elchi3 on 28 Aug 2018

@Elchi3 those two have been merged :) #2788 and #2686

connorshea on 10 Sep 2018

👍1

So I've put together a file that contains literally all the data from the old table for HTMLInputElement -- probably a little too much. I was just about to submit a PR, however the npm run test fails with an error regarding the JSON schema:

File : api/HTMLInputElement.json
JSON schema – 1 error(s)
item['api']['HTMLInputElement'] should NOT have additional properties

Not sure what I'm doing differently from all the other API files I see.
I'd love to submit a PR of my fork's dedicated branch but I'd hate to submit a non-functioning one. Any advice?

vinyldarkscratch on 27 Sep 2018

@vinyldarkscratch I’d say it’s fine to open a PR, and it’d help us figure out what the issue is :) based on the error I’d say you spelled a property wrong or got the hierarchy wrong somewhere.

connorshea on 27 Sep 2018

👍1

With #2770 now merged, the Web/API/Element task checkbox can now be checked.

ExE-Boss on 27 Sep 2018

🎉1

@vinyldarkscratch I did a quick "bisect" by deleting half the file and then checking if the linter still failed, and kept doing that until I had just the part of the file that was failing. It looks like the linter doesn't like that you have a feature called checkValidity(), but it passes just fine if you remove the ().

This line: https://github.com/vinyldarkscratch/browser-compat-data/blob/488444d0af64dae0b33de5618a481921269d4520/api/HTMLInputElement.json#L818

connorshea on 27 Sep 2018

Yeah, the only valid characters for feature names have to match the ^(?!__compat)[a-zA-Z_0-9-$@]+$ regular expression.

ExE-Boss on 27 Sep 2018

Oh my gosh, I feel dumb now, I totally missed the fact that I put parentheses in the feature name... XD Thanks, @connorshea, for looking into it! PR incoming soon. :wink:

vinyldarkscratch on 28 Sep 2018

@vinyldarkscratch someone else opened a PR for HTMLInputElement, though it’s only got a small number of the subfeatures so ¯\_(ツ)_/¯ I’d say you should still open yours.

connorshea on 28 Sep 2018

@ExE-Boss would the better-errors package have made those error messages easier to understand in this case? #2143

connorshea on 28 Sep 2018

@Elchi3 you’ll have to choose what to do between #2881 and #2884. Maybe merge the first one and then the second can be rebased on top of it? 2884 is definitely more comprehensive.

connorshea on 28 Sep 2018

(In reply to @connorshea from https://github.com/mdn/browser-compat-data/issues/2467#issuecomment-425469400)

@ExE-Boss would the better-errors package have made those error messages easier to understand in this case? #2143

Yes, it would. #2338 makes it so that schema validation errors are highlighted with a red underline in the log (see here for an example).

ExE-Boss on 28 Sep 2018

👍2

HTMLInputElement was merged and the article was updated, so I'm closing this issue. 🎉

connorshea on 18 Oct 2018

🎉1

Was this page helpful?

0 / 5 - 0 ratings

Related issues

Single/double spacing in notes?

vinyldarkscratch · 3Comments

Add <input> element compat data

Elchi3 · 4Comments

Move MDN feature table rendering to BCD project

jwhitlock · 4Comments

Thank you "issue"!

ghost · 3Comments

RTCPeerConnection.connectionState

TomasHubelbauer · 4Comments