| 05:11 | <sideshowbarker> | Sent a request to W3C systems team to update that. (I no longer have direct access myself to update it.) |
| 07:21 | <sideshowbarker> | ah — seems they’d already fixed it. I guess a request from Brian must’ve already bubbled up to them. |
| 08:02 | <zcorpan> | Patrick Meenan: ping https://github.com/HTTPArchive/httparchive.org/issues/971 |
| 14:35 | <jgraham> | I think one problem with requiring that scripts run in a content realm is what happens if that realm is navigated. With stream support in WebDriver I'm not sure if there are cases where we want to be able to access a stream once the underlying document has navigated (or worker has been discarded). I wonder a bit about downloads; if you want to stream a download which realm should that be associated with? If it's the global for the document that initiated the download the stream would certainly have to survive if that document was navigated. We also kind of wanted to use this mechanism to allow using the existing WebRTC specifications for screen capture, rather than rewriting all the details of how to capture a screen and get the data into a specified format and so on. That would certainly have to survive navigation and so wouldn't work if the spec depended on running algorithms in a specific content realm. |
| 19:32 | <Mattias Buelens> | Peter Linss: I've opened a PR for widlparser to properly support async_sequence<T>, PTAL 🙂 https://github.com/plinss/widlparser/pull/95 |