| 04:29 | <hsivonen> | hsivonen: https://www.w3.org/events/meetings/118f6c22-1545-4c3b-9581-260621fec362 - we've moved the session earlier |
| 08:45 | <nicolo-ribaudo> | Hi! I have a question regarding modules imports. When you dynamically import a module that is already in the modules map, does it yield to the event loop? My reading of the spec is "no", because it schedules a task to continue the import only when it performs an actual fetch, but both Firefox and Chrome seem to yield. They only settle the dynamic import promise in the current promise tasks queue if the import specifier is malformed. |
| 08:51 | <Ms2ger 💉💉> | https://html.spec.whatwg.org/multipage/webappapis.html#hostimportmoduledynamically(referencingscriptormodule,-modulerequest,-promisecapability) - the async returning doesn't seem particularly well integrated with the event loop |
| 08:57 | <nicolo-ribaudo> | Right, I'm removing it in https://github.com/whatwg/html/pull/8264 and I'm not 100% sure that I got that part correctly. |
| 10:45 | <hsivonen> | What mechanism makes the document.write in https://github.com/web-platform-tests/wpt/blob/master/html/browsers/browsing-the-web/navigating-across-documents/010.html not interfere with the load of href.html? |
| 10:45 | <hsivonen> | in Chrome that is |
| 10:46 | <hsivonen> | In Firefox currently, the mechanism is that the about:blank isn't the initial about:blank anymore, so the navigation does not reuse the inner window, so the document.write happens on the old (about:blank) document. |
| 10:47 | <hsivonen> | However, when inner window reuse takes place, which it presumably does in Chrome, what makes the document.write not blow away the new document that has become the document of the inner window while the event loop for the sync XHR was spinning? |
| 10:49 | <hsivonen> | When Chrome aborts the old fetches (including the XHR), does it also manage to abort scripts that are being executed so that the JavaScript program aborts before xhr.send() returns? |
| 10:49 | <hsivonen> | I guess I should test that hypothesis. |
| 10:54 | <hsivonen> | I can't log with console.log() from within the javascript: URL in Chrome. Is Chrome not executing the javascript: URL at all for some reason? |
| 11:26 | <Haerul Fuad> | smaug: smaug |
| 13:46 | <tashasyarifah> | Hi Tasha, what does "didn't work" mean? Did you get an error? |
| 14:23 | <Ms2ger 💉💉> |
|
| 14:23 | <Ms2ger 💉💉> | Is that the Cambridge comma? |
| 16:51 | <zcorpan> | tashasyarifah: did you click the triangle in " If signing as an Individual" or did you click the link "Individual"? |
| 16:52 | <zcorpan> | Maybe <details> here is confusing UI |
| 16:53 | <zcorpan> | and links in <summary> is certainly confusing UI (https://github.com/whatwg/html/issues/2272) |
| 16:55 | <Domenic> | nicolo-ribaudo: I guess we should match browsers here, and queue a task regardless. Even if IMO it would have been more elegant not to yield, this is what I get for using imprecise spec constructs; implementers used what they are familiar with / what is well specced (task yielding) and now we end up here. |
| 16:55 | <Domenic> | Web platform tests for this would be ideal if possible :) |
| 16:59 | <nicolo-ribaudo> | Yeah I agree that not yielding would be more elegant... I'll try to check how the other browsers behave; if they all agree or if there is inconsistent behaviour. |
| 17:54 | <zcorpan> | hsivonen: are you able to review https://github.com/whatwg/html/pull/8271 ? |
| 18:24 | <hsivonen> | hsivonen: are you able to review https://github.com/whatwg/html/pull/8271 ? |
| 18:53 | <zcorpan> | ty |
| 19:22 | <hsivonen> | AFAICT Chrome doesn't execute the javascript: URL at all on https://github.com/web-platform-tests/wpt/blame/master/html/browsers/browsing-the-web/navigating-across-documents/010.html . Safari, however, is really strange: onmessage sees document.write() winning over the href navigation but what the user sees is the href navigation--not the document.write. |
| 19:22 | <hsivonen> | Currently my local patch for Gecko has document.write winning both for script and rendering purposes. |
| 19:22 | <hsivonen> | Under what theory should document.write() not win? |
| 19:24 | <hsivonen> | That is, what's the logic that the test is trying to test? That aborting the javascript: URL navigation should abort the script excecution and not just the pseudo-network response resulting from the returned string? |
| 19:24 | <hsivonen> | jgraham: ^ |
| 21:02 | <Domenic> | (FWIW, I don't have any real answers here. Happy to approve a rename to .tentative, or maybe delete the test and open a whatwg/html interop issue so we can investigate and come up with what the answer should be.) |