| 02:12 | <gsnedders|ooo> | https://github.com/gsnedders/dom-test-suite has that old DOM testsuite in git, if anyone cares |
| 02:12 | gsnedders|ooo | forgets why he did that now |
| 04:58 | <Domenic> | We are still running versions of that suite for jsdom... maybe not necessary anymore... although given that we still can't mark WPT test files as partially passing, we might not be able to use WPT to replace all that coverage just yet. |
| 12:14 | <hsivonen> | Is https://w3c.github.io/DOM-Parsing/#the-domparser-interface the correct spec to read for DOMParser? |
| 12:41 | <annevk> | hsivonen: yes |
| 13:13 | <hsivonen> | annevk: thanks |
| 13:14 | <hsivonen> | TIL: Chrome adds the parseerror element as the first child of root in the document returned by DOMParser instead of following the spec |
| 16:00 | <jyasskin> | TabAtkins: Is there a good way for me to search Shepherd for uses of https://fetch.spec.whatwg.org/#concept-construct-readablestream? |
| 16:00 | <jyasskin> | And if so, is it documented somewhere I should have looked? |
| 16:02 | <TabAtkins> | jyasskin: https://tabatkins.github.io/bikeshed/#cli-refs , but I don't have a way to search by URL. |
| 16:03 | <jyasskin> | TabAtkins: I believe `bikeshed refs --text="construct a ReadableStream object"` searches for the definition, not the uses. |
| 16:04 | <TabAtkins> | Oh, I misread! |
| 16:04 | <jyasskin> | :) |
| 16:04 | <TabAtkins> | No, don't have that functionality yet, but it's on my shortlist. |
| 16:05 | <jyasskin> | I want to change the interface for that definition (https://github.com/whatwg/fetch/pull/781), but I'm worried I'll break uses outside Fetch. |
| 16:05 | <jyasskin> | TabAtkins: Would you mind looking it up for me? |
| 16:05 | <TabAtkins> | yup, taht's precisely the use-case I want it for. |
| 16:05 | <TabAtkins> | I don't have the *data* yet, so no. |
| 16:05 | <jyasskin> | Oh, ok. Thanks anyway. :) |
| 16:05 | <TabAtkins> | If I did, beleive me, the UI would be there immediately. |
| 19:56 | <Domenic> | So it appears document.open() can make the document's URL not equal to the URL of the corresponding session history entry. That's... fun. |
| 19:56 | <Domenic> | Can anyone think of other ways those things can get out of sync? |
| 19:56 | <Domenic> | smaug____: you may know ^ |
| 20:27 | <Domenic> | Tentatively TimothyGu and I believe this is very bad and should be fixed. A lot of the spec, and some impl code he dove through, assumes they are the same. |
| 20:29 | <rniwa_> | Domenic: what is very bad? |
| 20:30 | <Domenic> | rniwa_: document.open() can make the document's URL not equal to the URL of its session history entry |
| 20:31 | <rniwa_> | Domenic: oh, fascinating. |
| 20:31 | <rniwa_> | Domenic: so history.push(~) and then document.open() can move the URL back to the original URL |
| 20:31 | <rniwa_> | Domenic: but without adding a new history entry? |
| 20:31 | <Domenic> | Yeah also it breaks (per-spec) fragment navigation |
| 20:31 | <rniwa_> | oh snap |
| 22:02 | <smaug____> | Domenic: can't recall. (I wouldn't be surprised if something in pushState handling could lead to similar behavior though) |