Jacob Smith

I'm working on the repro, and I think I've got all the bits except for one final piece: When using Tab in puppeteer to focus on the date field (which...

I'm pretty sure that's not it: I captured a screen recording, and when viewing it frame-by-frame, it appears the yyyy is immediately selected as soon as the field is focused....

Circling back to this, the focus sequence is a real problem that prevents Puppeteer simulating a real (disabled) user, which is half the utility of the tests. I've tried to...

We found the cause of both issues (random/chaotic field focus and wrong sub-field focus within date/datetime fields): React's [reconciliation](https://legacy.reactjs.org/docs/reconciliation.html). TLDR: The workaround to set a tiny delay for Puppeteer whenever...

> @nodejs/collaborators @nodejs/tsc ... while this PR is not completely done, the lack of any review / feedback from contributors whatsoever is rather disheartening. If core contributors aren't interested in...

> have your flag take a value like --import-map=import-map.json Yes, exactly 🙂 > Whenever module customization hooks are registered, a new thread is spawned to run them. It would not...

I initially thought the `--(f)grep` was causing the setup file to get excluded (which _might_ make sense and thus be designed behaviour), but the file itself is run, so I...

Actually, it appears to be all CLI flags passed like `npm run foo -- --fgrep 'My Test'`

There **IS** (sometimes) a workaround, but it requires you to go about things in a very specific way: outdated: there's a better way (below) ```js // babyMaker.mjs import * as...

@thernstig probably yes. See my comment above for a potential workaround.