Research on WebIDL fragments in specifications and web engines.
My initial thought is to create an IDL index for all the web platform specifications that Crosswalk Project cares about, and to get a whole view of Web APIs it supports.
To my knowledge, Blink web engine that the Crosswalk Project relies on has some issues of its IDL fragments conforming to the W3C standard WebIDL. Thus we cannot leverage idlharness.js based test cases in Crosswalk Project testing.
Searching webidl in GitHub, I find some great repositories:
- heycam/webidl: primary repository in which the Web IDL specification is developed.
- darobin/webidl2.js: WebIDL parser.
- extensibleweb/webidl.js: an implementation of WebIDL in ECMAScript.
- othree/webidl: WebIDL files from Mozilla.
- dontcallmedom/webidl-checker: source code for the W3C on-line WebIDL checker, a tool verify the correctness of WebIDL fragments embedded in HTML documents.
Then I realize it is better to figure out the difference of WebIDL usage between specifications and web engines, moving forward from the IDL index.
All webidl files are from the latest specifications and web engines source code repositories.