Timothy Gu

> Couldn't we use the generated files exclusively? You can heuristically at least differentiate between interfaces and dictionaries, and we could just tag them directly. Yes, that differentiation in possible;...

> I guess I'd wait on solving the cross-package mixin use case until we have a concrete case. Okay. Other things we probably will not be able to use a...

Prettier has a stance of not changing ASTs, so I guess that'd be off. ESLint has [no-useless-concat](https://eslint.org/docs/rules/no-useless-concat), but sadly no fixer for it. This is easy to do even without...

Perhaps we can be a bit less ambitious, and separate out the parts that add [Exposed] support to `install()` (which I mentioned in #191) from the parts that aggregates globals...

I've rebased this, but it doesn't look like it's ready for review yet? Interface files call `webidl2jsGlobal.setupGlobal` but it's not defined.

For reference, Blink just uses a getter/setter rather than implementing each attribute individually: https://source.chromium.org/chromium/chromium/src/+/master:third_party/blink/renderer/core/css/css_style_declaration.idl;l=1;drc=fdd99242518b07d1d48e6f8453cbb7963a27cb6a. Gecko also has an IDL generation step: see https://searchfox.org/mozilla-central/source/dom/bindings/GenerateCSS2PropertiesWebIDL.py.

Just as a question: what DNS resolvers do browsers use?

Historically, I believe Gecko implemented `document.open` by creating a new realm and then "reparenting" existing DOM node objects to the new realm. That logic is since long gone, and assuming...

I see that people have started to add `GO111MODULE=auto` to a bunch of packages. However, according to https://blog.golang.org/go116-module-changes, that won't work in Go 1.17: > We plan to drop support...

@magician11 No your `new JSDOM(``, { url: '...' })` doesn't actually fetch the webpage. It merely sets the document URL. You still need `JSDOM.fromURL()`, which fetches the web page and...