Sebastian Mayr

Actually, adding jquery in there might make it leak, but I can't confirm that yet, might just be that the GC becomes much, much lazier. But it's definitely keeping the...

Nah, just makes the GC lazier, limiting the old size to 900mb keeps the used memory stable around 1GB.

@cpojer Are you generating actual `File` objects to put in there? Making `input.files` writeable is probably bad, we can probably either return the raw array to fill yourself, or do...

> Could we please get ESM export in JS Dom asap? :) We still support Node 10, probably until that (is very close to) EOL. ~~Even after that it'd probably...

> would you please collaborate with us on a solution to this interop issues which would not require node-fetch to depend on jsdom ? The problem here is that you...

> Use only JSDOM or no JSDOM at all isn’t a great solution for the community Not what I said. > there are & will continue to be use cases...

Looks like there's some movement in this whole thing with a draft spec [here](https://rocallahan.github.io/innerText-spec/). See also all the [references](https://github.com/rocallahan/innerText-spec/#references). There are no issues on the repo though, so I wonder...

Works with jQuery v1. Looks like we might run into some compat issues which were removed with v2.

There we go: jQuery 2.0 uses `offsetHeight` and `offsetWidth` to determine visibility (whereas it used multple factors in 1.0), however we don't have layouting in jsdom. This will probably not...

Yes, we won't be able so solve that without proper layouting (to properly calculate `offsetWidth`/`offsetHeight`). There might be a hack possible where you run through all parent elements and check...