| 03:05 | <noah> | this step of the ipv6 serializer is nutso "If compress pointer points to piece, append "::" to output if piece is address’s first piece and append ":" otherwise, and then run these substeps again with all subsequent pieces in address’s pieces that are 0 skipped or go the next step in the overall set of steps if that leaves no pieces." |
| 03:05 | <terinjokes> | ugh, I just stumbled into IDN |
| 04:12 | <terinjokes> | i have a headache now, sorry URL project for my ramblings ;) |
| 05:52 | <annevk> | terinjokes: IDNA is the good stuff |
| 05:54 | <annevk> | botie: tell smaug that WHATWG pull requests should have a link to a readable diff these days |
| 05:54 | <botie> | will do |
| 05:55 | <annevk> | botie: tell noah we can reword the IPv6 serializer to make it clearer |
| 05:55 | <botie> | will do |
| 06:54 | <terinjokes> | annevk: asking with my work hat one: is it recommended at this point that we start moving systems to IDA2008+non-transitional? |
| 06:56 | <terinjokes> | i discovered today that in different parts of the stack we're handling IDNs a couple of different ways |
| 07:03 | <terinjokes> | (i guess having one recommendation, even if that's IDA2003, is better than the random mix we seem to be doing right now) |
| 07:52 | <annevk> | terinjokes: my recommendation is UTS46 non-transitional |
| 07:52 | <annevk> | terinjokes: even UTS46 transitional uses a dataset that is modified-IDNA2008 |
| 07:53 | <annevk> | terinjokes: I'm hoping that Chrome and Edge will come around now Firefox and Safari have proven the way |
| 07:53 | <annevk> | terinjokes: there's definitely still pitfalls even if they all agree, but that's mostly to do with UTS46 |
| 08:14 | <annevk> | JakeA: mnot just found out that CORS cache issue Chrome has: https://github.com/whatwg/fetch/issues/307 |
| 08:14 | <annevk> | JakeA: seems surprising that it's still not fixed |
| 08:15 | <annevk> | JakeA: for all the security issues Googlers tweet about I sure find Chrome is rather lacking when it comes to its own same-origin policy breakage |
| 09:14 | <JakeA> | annevk: on holiday right now, but will chase this |
| 09:14 | <annevk> | JakeA: oh right, when are you back? |
| 09:15 | <annevk> | JakeA: anyway enjoy and please try to forget I pinged you about this |
| 09:30 | <annevk> | https://github.com/whatwg/html/pull/2421 is very exciting |
| 09:59 | <zcorpan> | hmm. the lint check for may in example doesn't work unless the class="example" and the may are on the same line. |
| 10:09 | annevk | unsubscribes from www-dom |
| 10:13 | <annevk> | www-dom used to be a great list for technical discussions about the DOM and then somehow it got turned into a process mess and now GitHub digests?! |
| 10:34 | Ms2ger | unsubscribes too |
| 10:44 | <annevk> | How long have default arguments worked in JavaScript function declarations? |
| 10:44 | <annevk> | Default argument values |
| 10:49 | <ondras> | http://kangax.github.io/compat-table/es6/#test-default_function_parameters ? |
| 10:50 | <annevk> | Thanks |
| 10:50 | <annevk> | It seems this very old looking XHR test was recently modified |
| 10:51 | <annevk> | I was thinking we had this feature for ages and I didn't know about it |
| 10:57 | <ondras> | :) |
| 10:57 | <ondras> | it is rather new, yes |
| 11:18 | <botie> | smaug, at 2017-03-08 05:54 UTC, annevk said: WHATWG pull requests should have a link to a readable diff these days |
| 11:21 | <smaug> | ah. This was pointerevers |
| 11:21 | <smaug> | events |
| 13:27 | <jgraham> | annevk: yt? |
| 13:27 | <annevk> | jgraham: yeah |
| 13:27 | <jgraham> | <<<<<<< cee5ae75919c5f22318f2e02d9b8a1dfd9fb66c5 |
| 13:27 | <jgraham> | var referrerOrigin = (new URL("/", location.href)).href; |
| 13:27 | <jgraham> | ======= |
| 13:27 | <jgraham> | var referrerOrigin = self.location.origin + '/'; |
| 13:27 | <jgraham> | >>>>>>> P3 Test referrer-policy in service workers. |
| 13:27 | <jgraham> | Which one is better? |
| 13:27 | <jgraham> | in fetch/api/policies/referrer-origin.js |
| 13:29 | <annevk> | jgraham: the second can emit non-ASCII in theory |
| 13:29 | <annevk> | jgraham: otherwise equivalent |
| 13:29 | <annevk> | jgraham: but I'd prefer no change I think since this is probably something where it was already fixed on WPT and Gecko also tried to fix it locally? |
| 13:32 | <annevk> | jgraham: if you're merging, any chance you can tell me about all fetch/xhr/cors/url/encoding/dom changes? |
| 13:32 | <annevk> | maybe not dom/ I haven't really investigated that much yet |
| 13:44 | <jgraham> | annevk: So the top one? |
| 13:44 | <jgraham> | Not sure what you want me to tell you? |
| 13:45 | <annevk> | jgraham: yeah don't change it (I hadn't actually looked at the resource to see what it was last changed to) |
| 13:51 | <jgraham> | annevk: I think the only changes are in fetch/ |
| 13:51 | <jgraham> | https://pastebin.mozilla.org/8981400 |
| 13:52 | <annevk> | ta |
| 16:22 | <terinjokes> | annevk: it looks like transitional UTF46 still converts ß to ss, which is how i fell down this rabbit hole |
| 16:23 | <terinjokes> | i agree though, it what i'll recommend internally |
| 16:57 | <annevk> | terinjokes: yeah, it ain't pretty |
| 17:21 | <Domenic> | annevk: terinjokes: I'm still wondering if we should spec the rule that implementations seem to have where short origins don't do validation or something... |
| 17:22 | <Domenic> | I can't find a tracking issue for that actually hmm |
| 17:23 | <annevk> | Domenic: short origin? |
| 17:23 | <Domenic> | Trying to find it... |
| 17:23 | <Domenic> | Like under 63 characters or something?? |
| 17:23 | <annevk> | Domenic: ASCII origins? |
| 17:23 | <Domenic> | Oh, that was it |
| 17:24 | <annevk> | Domenic: I am not having luck in talking to implementers and the UTS46 folks |
| 17:24 | <annevk> | Domenic: it's logged as an issue with them, still waiting for replies |
| 17:25 | <Domenic> | It'd be good to have a URL tracking issue |
| 17:25 | <Domenic> | Since one fix is on the URL side |
| 17:25 | <annevk> | Domenic: IDNA and file parsing are the main outstanding URL issues |
| 17:25 | <Domenic> | Just don't run ToASCII if it's already ASCII |
| 17:26 | <Domenic> | At this point I am pretty sure the discussion is not in whatwg/url... maybe it was in web-platform-tests |
| 17:26 | <annevk> | Domenic: sure, just waiting to hear back |
| 17:27 | <annevk> | Domenic: I wrote a post, there's also the Google doc linked from the IDNA issue |
| 17:28 | <annevk> | Domenic: anyway, feel free to open a dedicated issue, but without dialogue it's gonna be hard to do something |
| 17:29 | <Domenic> | Yeah, I just want something to track the issue, since this comes up in whatwg-url vs. browser conversations. I wrote https://github.com/whatwg/url/issues/267 . |
| 17:31 | <annevk> | Ta |
| 17:31 | <annevk> | I wish the IDNA folks were not mostly absent |
| 17:39 | <smaug> | Am I hallucinating: https://html.spec.whatwg.org/#event-loop-processing-model ends up creating /now/ using top level window.performance.now() and passing that value to also fAF callbacks in nested documents |
| 17:39 | <smaug> | the top level performance.now() may have nothing to do with child documents |
| 17:41 | <smaug> | zcorpan: you might have something to say about ^ |
| 17:46 | <terinjokes> | Domenic: is there a problem applying ToASCII on ASCII-only imput? |
| 17:47 | <terinjokes> | as someone who's currently doing that across multiple environments, i thought it was mostly safe |
| 17:47 | <Domenic> | terinjokes: it does extra validations like a length limit or disallowing leading hyphens. Apparently browsers don't do that unless the input contains unicode. |
| 17:50 | <smaug> | https://github.com/whatwg/html/issues/2423 |
| 17:50 | <annevk> | terinjokes: https://annevankesteren.nl/2017/02/idna-toascii-differences |
| 17:50 | <annevk> | Domenic: I'm still interested in filing incumbent settings object bugs |
| 17:51 | <annevk> | Domenic: for much the same reasons as you're interested in having that IDNA issue filed |
| 18:22 | <Domenic> | annevk: sure, if you want, but I don't know what they would say... "the spec currently says something, but we're not sure about it, so please don't change anything yet until we figure out our story?" |
| 18:23 | <annevk> | Domenic: hmm, so bz seems confident |
| 18:23 | <annevk> | Domenic: but I guess if you're not done yet, we can wait |
| 18:23 | <annevk> | Domenic: but it seems like you've been putting in a lot of effort without much guidance from non-Fx |
| 18:24 | <Domenic> | I mean I think we are reasonably confident about the definition of incumbent. Just not its usage sites. |
| 18:24 | <Domenic> | And there's also the possibility that if we get the number of usage sites down low enough, having a high-fidelity incumbent doesn't matter much, so we could simplify the definition to what non-FF UAs do. |
| 18:29 | <annevk> | Okay, guess I'll try to be more patient |
| 18:38 | <annevk> | I mean, I will be more patient and thank you for sorting this out, I'm not jealous |
| 18:44 | <Domenic> | :) |
| 18:55 | <annevk> | Domenic: transfering a stream or anything that spans multiple tasks is best done by associating a private MessageChannel with the object I think |
| 18:56 | <annevk> | Domenic: so you have a ReadableStream on both sides, each with their own MessagePort and MessagePort handling logic |
| 18:56 | <annevk> | Domenic: and then you transfer the objects through that MessageChannel |
| 18:57 | <annevk> | Domenic: the initial clone would set up the MessagePort logic |
| 18:57 | <annevk> | Domenic: I can't really think of another primitive that would make something like that work |
| 18:58 | <annevk> | Hmm, alshamiri1 is listed as reviewer on all HTML PRs despite not having a GitHub account |
| 19:03 | <annevk> | I guess I'll complain to GitHub |
| 19:07 | <Domenic> | A private MessageChannel, wow, I never thought of that |
| 20:40 | <Domenic> | It's strange but nice that both Gecko and Chrome seem to suddenly be working on making the text selection APIs interoperable |
| 22:24 | <wanderview> | argh... why does the service worker spec link to TR for this? https://www.w3.org/TR/page-visibility/#dom-document-visibilitystate |
| 22:25 | <wanderview> | I guess there is no draft version? |
| 22:34 | <Domenic> | wanderview: there is, https://w3c.github.io/page-visibility/ |