Decide what to do with comments

[saschanaz]

Currently there are two ways to fetch comments

1. From MDN
2. From specs

Both are not being actively maintained. I think either one should be dropped and replaced by another one.

[MattiasBuelens]

FYI: It looks like the fetch-comment and fetch-mdn scripts are now both broken.

• fetch-comment requires inputfiles/idlSources.json, which was removed in Remove redundant files and types #1044.
• fetch-mdn requires inputfiles/browser.webidl.preprocessed.json, which was removed in Merge types_web back into TypeScript DOM lib generator #1034.
• fetch-mdn tries to fetch JSON files from MDN using the URL template https://developer.mozilla.org/en-US/docs/Web/API/${name}$json (where ${name} is the name of an IDL interface), but this no longer works. For example, https://developer.mozilla.org/en-US/docs/Web/API/ReadableStream$json returns HTTP 404. There doesn't seem to be an official machine-friendly API anymore... 😕 The best we can do would be processing the Markdown source files from https://github.com/mdn/content, such as https://github.com/mdn/content/blob/main/files/en-us/web/api/readablestream/index.md.

[saschanaz]

Safari DevTools seemingly imports comments for CSS properties from somewhere, not sure it's MDN or not. I hope there's a better way since both of the previous ways were all hacky.

[Bashamega]

Hello @saschanaz
I think this should be closed, because I have updated the comments in #1940

[saschanaz]

Good point, closing.