| 01:15 | <littledan> | annevk: well, if Chrome uses V8's microtask queue, at least it seems like that would make it the odd one out: Both WebKit and Gecko seem to include microtask queues in their JS engines just for testing kinds of purposes, and swap that out for something provided by the renderer when it's there. (I hope this doesn't cause problems for people who hope that tests run in the JS shells match how things would work on the web! A lot |
| 01:15 | <littledan> | of testing is done in JS shells) |
| 08:17 | <annevk> | littledan: maybe that shows either setup can work |
| 10:00 | <jochen__> | how would you implement microtasks in a spec compliant fashion if you don't share the queue with the ecmascript engine? |
| 10:03 | <annevk> | jochen__: the engine could call something in the host and let the host deal with the queue |
| 10:09 | <jochen__> | yeah, but you still need one central queue |
| 10:09 | <jochen__> | doesn't really matter where it lives |
| 10:10 | <annevk> | jochen__: sure, as long as it meets the needs of both sides all is good |
| 10:10 | <annevk> | jochen__: the main issue is that the current spec setup between ES and HTML is broken (or at least not great) |
| 10:10 | jochen__ | is shocked |
| 10:11 | <annevk> | Uhuh, film at 11 |
| 10:58 | <nox> | Can we go to the premiere? |
| 10:58 | <nox> | Doing some HTML tests this morning. |
| 11:25 | <nox> | annevk: Hah! |
| 11:25 | <nox> | annevk: <script></script><iframe> <- Neither Safari nor Chrome can observe the iframe's content window when running the script. |
| 11:25 | <nox> | Only Firefox does that. |
| 12:36 | <annevk> | wat |
| 12:37 | <annevk> | They actually create it from this queue? Madness |
| 12:39 | <annevk> | I wonder if that can be used somehow where something assumes that a frame being in the tree assumes that it has a bc |
| 12:39 | <annevk> | The various window getters for instance |
| 12:45 | <nox> | annevk: Don't know |
| 12:46 | <nox> | https://twitter.com/nokusu/status/1097477426995695616 š¤” |
| 12:47 | <nox> | annevk: The maddest part of it all, |
| 12:47 | <nox> | annevk: is that jdm added the queue in Servo specifically for script/iframe issues. |
| 15:17 | <annevk> | nox: we could probably create the nested browsing context from this queue, but it would require further tests |
| 15:17 | <annevk> | nox: would also be nice to understand why Chrome does that |
| 15:17 | <annevk> | nox: thanks for going down the rabbit hole though |
| 15:18 | <annevk> | nox: making a lot of progress over where we got to last time around |
| 15:18 | <gsnedders> | ā„ļø yu guys for working on this |
| 15:51 | <nox> | annevk: You are welcome! I just donāt want Servo to introduce yet another different behaviour. :) |
| 15:53 | <nox> | annevk: I meant that Servo introduced the queue to run scripts *because* it was causing issues that iframes could have their contentWindow be null |
| 15:53 | <nox> | Thatās why Chrome not initialising they beforehand either surprised me. |
| 15:53 | <nox> | Them* sorry currently on my phone |
| 15:54 | <annevk> | nox: did you run blame on that change and does it have any useful data? |
| 15:55 | <annevk> | nox: e.g., the code that somehow worked in Chrome yet did not in Servo |
| 15:56 | <nox> | annevk: So I was on the Servo channel and I saw an issue about a refactoring for the "deferred scripts" in Servo, |
| 15:56 | <nox> | I didn't know "deferred scripts" were a thing because that was introduced last year when I was kidnapped to work on WebGL, |
| 15:56 | <nox> | I just assumed that the change was made to follow the behaviour of both Firefox and Chrome but clearly I was wrong about that. |
| 15:56 | <nox> | I'll look up into it and ask jdm more details. |
| 15:58 | <annevk> | I forgot who pointed me to Mode::Rfc2045 in WebKit's new MIME type parser (maybe Domenic?) but it seems like this is mostly harmless. It's considered deprecated and a way to find old callers that need yet to be migrated. Time will tell I suppose. |
| 17:00 | <nox> | annevk: I can't observe referrer policy without doing a request, right? |
| 17:02 | <Domenic> | annevk: on vacation until Thursday, FYI. I'll merge the review draft things though. |
| 17:11 | <annevk> | nox: think so |
| 17:11 | <annevk> | Domenic: thanks and good to know |
| 17:12 | <nox> | annevk: So I can insert a script and a meta, and make a request from that script to observe referrer policy changes then. |
| 17:12 | <annevk> | I think so |
| 17:29 | <annevk> | nox: you might be able to reuse logic from referrer-policy/ tests btw |
| 17:29 | <nox> | annevk: Ok! |
| 20:19 | <nox> | annevk: Found a bug in the spec I think. |
| 20:19 | <nox> | annevk: "If a source element is inserted as a child of a media element that has no src attribute and whose networkState has the value NETWORK_EMPTY, the user agent must invoke the media element's resource selection algorithm." |
| 20:19 | <nox> | "The resource selection algorithm for a media element is as follows. This algorithm is always invoked as part of a task," |
| 20:19 | <nox> | First quote is not part of a task right? |
| 20:26 | <annevk> | nox: it is |
| 20:27 | <nox> | annevk: Oh ok |
| 20:27 | <annevk> | nox: queued by the parser or a task that runs some script |
| 20:27 | <nox> | Oh right. |
| 20:27 | <nox> | annevk: And should media.networkState ever be undefined? |
| 20:28 | <annevk> | nox: perhaps we should remove that though as everything on the main thread is part of a task pretty much |
| 20:28 | <annevk> | nox: not sure, foolip would know |
| 20:31 | <nox> | http://software.hixie.ch/utilities/js/live-dom-viewer/?saved=6629 |
| 20:31 | <foolip> | nox: It'ss never the value undefined, always one of the enum integer values. But there may be cases where the spec doesn't make things unambiguously clear |
| 20:32 | <nox> | foolip: http://software.hixie.ch/utilities/js/live-dom-viewer/?saved=6630 What am I doing wrong then? |
| 20:32 | <nox> | Err, without the confusing window named getter usage: http://software.hixie.ch/utilities/js/live-dom-viewer/saved/6631 |
| 20:32 | <innovati> | When working with HTML, it's easy to convert from HTML syntax to XML syntax by using DOMParser and XMLSerializerā¦but going from XML syntax to HTML syntax doesn't seem as straightforward. What's the correct way go about that? What should happen to namespaces? |
| 22:08 | <foolip> | nox: there is no <media> element, just <audio> and <video> |
| 22:45 | <nox> | foolip: I knew the explanation would be me extremely clueless about something š |