Consider excluding IDLs from Web Incubator CG
We can index off a IDL name into
https://github.com/w3c/webref/blob/main/ed/dfns/
And then look for the spec location. Might remove a LOT of noise and churn from the generated IDLs!
See https://github.com/w3c/webref/blob/d69ef53f2a4ca9b3a58c23bb1d2544f3d12e48cd/ed/dfns/turtledove.json#L4
Ooo! We can use https://www.npmjs.com/package/web-specs – this has the corresponding names!
CC @srujzs
Another source of info we could use is the experimental flag from the MDN web docs:
https://developer.mozilla.org/en-US/docs/MDN/Writing_guidelines/Experimental_deprecated_obsolete
From that page, features graduate out of experimental if "[they are] supported by default in two or more major browser rendering engines".
Perhaps close this issue (and track exposing specific APIs in other issues?)?
Perhaps close this issue (and track exposing specific APIs in other issues?)?
YES!
I don't want to resolve this one quite yet - I still want to tackle opening up the API surface a bit more (standard && !experimental) and the changes needed for that.