Philip Jägenstedt

Basically what `document.write` does is to add text to the input stream of the parser just as if it had arrived on the network (and been decoded) so knowing it...

@npm1 can you describe what is going to ship in Chromium, and can the spec be updated to reflect that if it's a conservative approach? I spotted a link to...

At TPAC this year, @thejohnjansen noted that the EDP implementation had heavily used Chrome's tests, and in fact *only* on those tests and not reverse engineering CDP in Chrome. Quite...

@brendyna that sound really exciting! Could you paste a representative test so I can understand the structure a bit? When we integrate this into web-platform-tests they will need some special...

Editing on GitHub so I didn't update index.html.

@rayankans can you ensure that installedApp’s id is also a URL so that this is well defined?

This is mentioned non-normatively in domintros of [`getFile()`](https://wicg.github.io/native-file-system/#api-filesystemdirectoryhandle-getfile) and [`getDirectory()`](https://wicg.github.io/native-file-system/#api-filesystemdirectoryhandle-getdirectory), which say "can fail because [...] the name uses characters that aren’t supported in file names on the underlying file...

Thanks for the details, @mkruisselbrink! I see that @Hexcles reviewed https://chromium-review.googlesource.com/c/chromium/src/+/1989369, but cc @LukeZielinski @stephenmcgruer for visibility. It sounds like a fairly simple WebDriver API in the style of `setFilePathForMockFileDialog...

This is done now, right, or do we want to go even further back?

Here's a screenshot from inside the VM: