| 04:36 | <domfarolino> | Ugh, we need to implement async iterators |
| 04:36 | <domfarolino> | It kinda fell off the priority wagon last year (for Chrome at least) |
| 04:51 | <Domenic> | Plzzz |
| 09:37 | Ms2ger | tries to remember if this is a good time to catch MikeSmith |
| 10:39 | MikeSmith | Ms2ger here now |
| 10:53 | <MikeSmith> | botie: inform Ms2ger remind to me to follow up |
| 10:53 | <botie> | will do |
| 11:18 | <MikeSmith> | PSA https://www.w3.org/TR/cors/ now redirects to https://fetch.spec.whatwg.org/ |
| 11:19 | <MikeSmith> | PSA2 https://www.w3.org/TR/notifications/ now redirects to https://notifications.spec.whatwg.org/ |
| 11:21 | <annevk> | MikeSmith: cool, maybe Fetch no longer needs to say it replaces CORS |
| 11:21 | <MikeSmith> | annevk: yeah I guess it’s no longer necessary |
| 11:24 | <MikeSmith> | oh, that reminds me — one more: https://www.w3.org/TR/progress-events/ » https://xhr.spec.whatwg.org/ |
| 12:03 | <botie> | Ms2ger, at 2020-06-02 10:53 UTC, MikeSmith said: remind to me to follow up |
| 12:04 | <Ms2ger> | botie, inform MikeSmith reminder |
| 12:04 | <botie> | will do |
| 12:29 | <MikeSmith> | about https://github.com/whatwg/xhr/pull/279#issuecomment-636987348 — can I resolve this by adding a note to https://developer.mozilla.org/en-US/docs/Web/API/XMLHttpRequest/send#Syntax saying that no browsers actually yet implement support for XMLHttpRequest.p.send(body) with a ReadableStream? |
| 12:29 | <botie> | MikeSmith, at 2020-06-02 12:04 UTC, Ms2ger said: reminder |
| 12:31 | <annevk> | MikeSmith: I see two issues there; it doesn't clearly allow for null as a value |
| 12:32 | <MikeSmith> | OK |
| 12:32 | <annevk> | MikeSmith: and ReadableStream could just be removed, I don't think we need a note as it was never implemented and won't be added per this decision |
| 12:32 | <MikeSmith> | yeah now looking at https://github.com/whatwg/fetch/pull/1029 I see the plan there |
| 12:38 | <MikeSmith> | annevk: OK how does https://wiki.developer.mozilla.org/en-US/docs/Web/API/XMLHttpRequest/send#Parameters look now? |
| 12:40 | <annevk> | MikeSmith: seems good; I think for developer documentation we could do more to unpack USVString and BufferStream and such, but that's a more global issue I suspect |
| 12:40 | <MikeSmith> | yeah |
| 13:30 | <annevk> | Domenic: define browsing session as the new 7.7.1? At the start of Session history and navigation |
| 13:30 | <annevk> | And what, I mean a glorified XXX entry |
| 13:30 | <annevk> | And with that* wow |
| 13:34 | <Domenic> | annevk: seems reasonable. The other thing would be as the new 7.1 since it's conceptually "larger" than a browsing context, but, I think your idea is probably better. |
| 13:35 | <annevk> | It's larger than a top-level browsing context, and smaller or larger than a BCG, depending |
| 13:36 | <annevk> | Good times in browsing * land |
| 14:05 | <domfarolino> | Domenic: ping on https://github.com/whatwg/html/pull/5573 in case you wanted to merge |
| 14:05 | <Domenic> | Ah thank you |
| 15:09 | <domfarolino> | When did PR preview stop showing the yellow highlights and arrows in the diff view? |
| 15:13 | <Domenic> | I noticed that too... |
| 15:31 | <domfarolino> | It makes the diff so hard to read for HTML PRs because the pages are so big usually :/ |
| 15:42 | <Domenic> | Worth filing an issue... https://github.com/tobie/pr-preview/issues |
| 15:43 | <annevk> | Is it only the styling that is lost? |
| 15:43 | <annevk> | I still see <ins> plus class in the source, but it's not highlighted as much as it used to be |
| 15:44 | <annevk> | Oh I see |
| 15:44 | <annevk> | I think we broke it when we moved out <style> |
| 15:45 | <annevk> | I didn't realize how much this script modified our output |
| 15:45 | <annevk> | It also tries to load https://w3c.github.io/htmldiff-nav/index.js |
| 15:49 | <annevk> | It also forces quirks mode |
| 15:52 | <annevk> | https://github.com/tobie/pr-preview/issues/66 |