| 06:16 | <smaug> | Domenic: curious, how are you reviewing the session history rewrite, I mean using what kinds of tools? |
| 08:17 | <hsivonen> | I found another Chromium-originating WPT that assumes that on non-initial about:blank, location.href == "about:blank" implies that the about:blank DOM has been built. Still no idea if this is a thing test authors assume or a thing that Web authors also assume. |
| 08:18 | <hsivonen> | I found another Chromium-originating WPT that assumes that on non-initial about:blank, |
| 08:21 | <hsivonen> | https://github.com/web-platform-tests/wpt/blob/master/content-security-policy/inheritance/window-open-local-after-network-scheme.sub.html Location object should update when a new Document is created by the parse as opposed to being deferred to the end of the parse: https://html.spec.whatwg.org/#concept-location-url |
| 08:42 | <hsivonen> | Hmm. Chromium seems to force synchronous HTML parsing for javascript: URLs. Is there a justification for that? (Gecko doesn't do that.) |
| 08:49 | <hsivonen> | I suspect Chromium's implementation of how about:blank URLs result in a (zero-length) stream of data might have the side effect of the HTML tokenizer getting pumped to EOF in the same task that creates the Document object. Is that the case, Yoav Weiss ? |
| 08:51 | <hsivonen> | My current patch removes the remains of the Netscape-era HTML parser that we were using for about:blank only, but it looks a lot like I might have to re-introduce an about:blank-specific parser or parse mode for non-initial about:blank if Web sites assume what Chromium-originating WPTs assume. :-( |
| 08:55 | <hsivonen> | Are extensions in Chromium allowed to cause an asynchronicity point in HTML tree building of a from-stream-parsed document? That is, do the WPT assumption of non-initial about:blank element nodes getting created in the same task as the document hold if Chromium instances that have arbitrary extensions installed? |
| 09:02 | <hsivonen> | I guess I'm going to implement a special about:blank mode for the main HTML parser in Gecko and see what happens with WPTs. I think this is sad. |
| 10:08 | <Domenic> | Domenic: curious, how are you reviewing the session history rewrite, I mean using what kinds of tools? |
| 10:12 | <smaug> | Just wondering if there is something good for such a massive patch |
| 12:27 | <hsivonen> | I guess I'm going to implement a special |
| 12:28 | <hsivonen> | (Hmm. Somehow, GitHub didn't offer me the issue template for that one.) |
| 14:13 | <annevk> | We only have a template for PRs. |
| 15:50 | <hsivonen> | Jake Archibald: What are the navigation behaviors that are interoperable but "too wrong to put in the spec"? |
| 15:51 | <hacknorris> | i would want too |
| 15:53 | <Jake Archibald> | hsivonen: https://github.com/whatwg/html/issues/8273 is one. Also this one https://youtu.be/W6lvQvdeF8U?t=793, although we fixed that in Chrome |
| 16:04 | <hsivonen> | hsivonen: https://github.com/whatwg/html/issues/8273 is one. Also this one https://youtu.be/W6lvQvdeF8U?t=793, although we fixed that in Chrome |
| 20:18 | <jgraham> | So WebDriver-BiDi wants to inject some scripts that run before any other script on the page (maybe before any DOM is constructed? That would be more deterministic, but maybe unnecessary if it's hard). I'm not sure quite where the right place to execute those scripts is in terms of the HTML spec. Can I do it right after the environment settings object for the new Window is created (i.e. after 6.9 in https://html.spec.whatwg.org/#initialise-the-document-object) or should I be looking elsewhere? |