Process for updating browser.webidl.preprocessed.json?

The readme says that browser.webidl.preprocessed.json is a JSON file generated by Microsoft Edge, not to be updated. It looks like it was last updated in April 2019.

addedTypes.json, however, seems to be often updated.

Which brings me to my question: is a new approach needed to get more of the definitions via (semi) automated processes, rather than adding types by hand? I also do some work on webref (scraped IDL from specs) and BCD (browser compat data) and this is what comes to mind:

Match up IDL definitions with BCD entries. For IDL definitions missing in TSJS-lib-generator where BCD says the APIs are supported, propose those for inclusion in TSJS-lib-generator. The precise rules for what level of support is necessary can be debated.

There would be additional work to ensure that BCD keeps getting new entries based on additions to webref, of course, but that’s something @vinyldarkscratch and I are already working on separately in https://github.com/foolip/mdn-bcd-collector.

[foolip]

Thanks @saschanaz! I agree that trying to differentiate WHATWG and W3C specs doesn’t seem very useful, but hopefully I won’t run into that. I hadn’t seen removedTypes.json, thanks for pointing that out.

Currently I’m not removing types that are widely supported but nonstandard. I think such things should be specced anyway.

I agree, but don’t think there will ever be a point in time when the sum of all spec IDL adds up to something consistent and covering everything shipped in any browser, so some manual curation of IDL seems necessary. I’d like to avoid it though, if the problem becomes small enough.

[github-actions[bot]]

Closing because @saschanaz is one of the code-owners of this repository.