| 07:28 | <nox> | annevk: How dare you make overt declarations of war? |
| 07:34 | Ms2ger | throws a spear at nox's temple |
| 07:34 | <nox> | :) |
| 14:36 | <nox> | This is amazing. |
| 14:37 | <jgraham> | nox: Glad you think so |
| 14:38 | <nox> | "Only Chrome" "Ok Chrome and minor input from others" "Ok browsers but what about the rest" |
| 14:38 | <nox> | Goalposts moving faster in space than Usain Bolt. |
| 14:40 | <jgraham> | nox: You might have to tell me what the context is |
| 14:40 | <jgraham> | :) |
| 14:40 | <nox> | jgraham: I understand your confusion now, |
| 14:41 | <nox> | you live in an universe where people find new windmills, |
| 14:41 | <nox> | but they don't in ours: https://github.com/whatwg/url/issues/118#issuecomment-337742987 |
| 14:41 | <nox> | Good old URL drama |
| 14:54 | <nox> | Ah ah I only now noticed "https://///url.spec.whatwg.org/ writes that the goal of the WHATWG is to" |
| 14:54 | <nox> | With the //// |
| 14:59 | <annevk> | nox: magcius is correct btw, address bar is UX |
| 15:00 | <nox> | annevk: I don't remember disagreeing with that, so maybe I miswrote something. |
| 15:00 | <annevk> | Not sure where all the anger is coming from with the others |
| 15:00 | <annevk> | Why waste time on failed standards? |
| 15:01 | <nox> | annevk: Oh yes, for me the address bar isn't part of the Web platform. |
| 15:01 | <nox> | annevk: So I wasn't disagreeing with that part of it, I was just also writing down that it's not just about the HTML source. |
| 15:01 | <annevk> | Fair |
| 15:02 | <nox> | But it wasn't very clear indeed. |
| 15:02 | <nox> | annevk: That Safari copes with /// from JS but not from the address bar is quite unfortunate, TBH. |
| 15:29 | <annevk> | nox: why? |
| 15:37 | <nox> | annevk: Am just weirded out by the fact that it somehow ends up looking up localhost from the address bar. |
| 16:08 | <annevk> | oh |
| 17:19 | <Domenic> | Hmm I was hoping to counteract the Safari narrative using https://wpt.fyi/url but the old version of Safari used there doesn't help our case. The new version should be very green though. |
| 17:21 | <jgraham> | Domenic: Yes, so getting OSX at all is a pain. And getting OSX with a non-default Safari is an even bigger pain. It currently uses Sauce |
| 17:23 | <jgraham> | Safari 10 is the latest avaiable |
| 17:23 | <jgraham> | On sauce |
| 17:26 | <Bakkot> | am I reading https://html.spec.whatwg.org/multipage/common-dom-interfaces.html#HTMLAllCollection-call correctly as implying `document.all() === null`? |
| 17:26 | <Bakkot> | both Chrome and Safari give undefined, not null, is why I ask |
| 17:26 | <Bakkot> | And Firefox throws with “too few arguments" |
| 17:30 | <Bakkot> | actually, I see safari has switched to returning null sometime between stable and tech preview |
| 17:39 | <Bakkot> | ah, yes, I see that’s tested. https://github.com/w3c/web-platform-tests/blob/41f06d4c660aa97ba9ec08be03723460bdfd6c96/html/infrastructure/common-dom-interfaces/collections/htmlallcollection.html#L218 |
| 18:24 | <Domenic> | Bakkot: yeah, there hasn't been great interop, but things are getting better. |
| 18:43 | <jsx> | If a browser is using USVString for one API which asks for CSSOMString (say for FontFace), is it guaranteed that it will be using USVString for all instances for CSSOMString? |
| 19:47 | <TabAtkins> | jsx: Yes. https://drafts.csswg.org/cssom/#cssomstring-type (The definition is actually that it's one or the other, not (DOM or USV).) |
| 19:49 | <jsx> | Ok, I just wanted to confirm that the the choice is universal across all APIs in that browser |
| 19:51 | <TabAtkins> | Per spec, yes it is. |
| 19:52 | <jsx> | Ok, thanks. |