Import compatibility information from Chrome documentation about browser-compat-data

[jpmedley]

FYI, these are extensions that are particular to Chrome. Chrome Developer Relations doesn't document these on MDN for this particular reason. If any of these features are on MDN, it's because someone else has put them there. Joe Medley | Technical Writer, Chrome DevRel | [email protected] | 816-678-7195 *If an API's not documented it doesn't exist.*

…

On Tue, Jun 13, 2017 at 10:12 AM, Sebastian Noack ***@***.***> wrote: The Chrome documentation <https://developer.chrome.com/extensions/api_index> provides more accurate compatibility information for some (though not all) APIs than what is currently shown on MDN. I hacked together a Python script <https://gist.github.com/snoack/bf61cca7a1b7f39fefe848db70031ac9> that imports compatibility data for APIs we have listed here, that have explicit compatibility information in the Chrome documentation. Here <https://gist.github.com/snoack/b10d29d26847018b493a9f740a2db164> is how the changes generated by the script would look like. If these look sensible to you, I can open a pull request, or you could just run the script yourself. Otherwise, I'm also happy to make changes to the script, in case I missed something. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#243>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AH0vi5KBytYVc0AHwzG3F71GfHYbZ2VNks5sDsMFgaJpZM4N4y3t> .

[wbamberg]

@jpmedley , this data is used in the WebExtensions documentation on MDN. WebExtensions are a cross-browser system for developing browser extensions, based on Chrome's but also supported by Edge and Firefox.

@snoack , this is also very cool. I'll get back to you on how we should move ahead with this :).

[snoack]

@jpmedley: I don't see how being a vendor specific API is a reason to not document it on MDN. There are a few non-standard DOM and JavaScript APIs, that aren't implemented in Gecko, documented on MDN. As far as WebExtensions go, some features that are only implemented in Chrome and/or Opera are already documented on MDN as well. Not to mention that some (if not most) of the API features, I try to pull in data for here, are actually implemented in Firefox, and I just try to improve the accuracy of the compatibility data on MDN.

@wbamberg: I already found some issues with my import script and the changes it produces. Meanwhile, I started to improve the data progressively and (semi-)manually, as you have seen in my recent pull requests. The advantage of manually revising the data is that I find (and fix) other issues, and add compatibility information for other browsers, while on it. On the other hand it is a very cumbersome process and I will ultimately miss something (or lose interest​ at some point). Then again, even when I improve the script, it will still produce quite some cases of version_added: null which need to be cleaned up manually.

[wbamberg]

@snoack , we had a conversation about this, and would be very happy to take a look at PRs generated automatically, if you are still interested in this approach.

[snoack]

Cool. I will start looking again into importing compatibility data from the Chrome documentation. There are some improvements to be done to my script. Not sure though, when exactly I will get around to it.

[Elchi3]

There has been no activity here. I'm closing this as we're not planning to work on this any time soon. If you want to come back to the idea, feel free to reopen this issue.