Add more comments

[Bashamega]

related to #1940
Hello:)
In my last PR I have used MDN to generate comments for interface declarations, in this pr I add it for the properties.

[github-actions]

Thanks for the PR!

This section of the codebase is owned by @saschanaz - if they write a comment saying "LGTM" then it will be merged.

[Bashamega]

Not ready for review
Ready for review

[saschanaz]

I'm yet to review this, but please do not convert to sync APIs.

[Bashamega]

I'm yet to review this, but please do not convert to sync APIs.

Sure

[Bashamega]

Hello @saschanaz
I have switched the old functions to async, but the new function is still sync because the emitter is not async. I tried switching it to async, but it broke.

[Bashamega]

I have updated the context to not call the API in the emitter, but that cause the test to fail, I will fix it later

[Bashamega]

Done @saschanaz

[saschanaz]

LGTM 🎉

[github-actions]

There was an issue merging, maybe try again saschanaz. Details

[Bashamega]

Thank you very much @saschanaz

[jakebailey]

After this, there's nothing else to comment on, right? This is as large as we're going to get?

Each one of these makes parsing the DOM types slower, so I'm hoping that we stop at some point 😅

[saschanaz]

Technically we still have events, but adding comments there would be a bit awkward as that would only work for onevent attributes and not for addEventListener calls. Probably fair to just skip that.

[saschanaz]

LGTM

[github-actions]

Merging because @saschanaz is a code-owner of all the changes - thanks!

[Bashamega]

Hello @jakebailey
First of all, thank you very much for merging this pr.
Secondly, I think we can improve the compiler's speed by caching comments in a JSON file, which will serve as the comments reference. The GitHub action will be responsible for updating it. If this sound good to you, I can draft a pr for it and compare the speed.
Also, there are still some missing comments.

[jakebailey]

I don't know what you mean, sorry. The comments have to be in a declaration file. Moving them elsewhere won't speed things up (and will make the compiler/editor stuff challenging).

[Bashamega]

I don't know what you mean, sorry. The comments have to be in a declaration file. Moving them elsewhere won't speed things up (and will make the compiler/editor stuff challenging).

I mean instead of fetching the data each time you run the generate command, we can put the comments in a json file and the builder will use that json file instead of fetching the summaries every time

[HolgerJeromin]

I am pretty sure Jake meant the usage (in the editor and compile of user code) of the generated files will slow down the typescript compiler as it has to parse more data.
Build/generation time of these files is uninteresting.
tsdoc belongs into the .d.ts file and not in a (faster?) parallel world which needs to be invented and maintained.