jerch

@Tyriar Ready for review. Note that I changed `performance.now` to `Date.now`, which also fixes `IdleTaskQueue` for nodejs.

@Tyriar Oh well - should we still change the rescan logic as described here? > I think a slightly more advanced logic might avoid all those re-scan refforts: > >...

Holy cow, just tested it and what can I say - **never underestimate the effect of exp growing**, even for cheapo tasks like rescanning arrays in JS. Here are some...

@Tyriar Thx for insisting on the lower batch size in the first place, helped me to think around the nonsense re-scan penalty with exp growth - this runtime is better...

This happens, if the recorded terminal data contains requests, which the terminal will respond to (here DA2). To fix that - replay first on the new terminal, then connect to...

No I have not solved it, as I dont had the issue. I've posted here, because we got a similar question in the xterm.js repo.

@Tyriar Really nice to get those rolling now we have puppeteer. Once they reach a critical coverage, we can even get rid of the terminal tests with those ugly escape...

Created PR #649, which fixes this issue for the demo site.

:scream: If you want to go that route, maybe I can help here and there. Some early remarks: Would it be possible to run the the terminal core without Qt...

> But, @jerch, I do not want to backstab you and your actual project! :-) No worries, I am in exploring mode regarding wasm anyway. > I am however curious...