| 01:21 | <MikeSmith> | Stackoverflow finally moving away fully from non-TLS https://meta.stackexchange.com/questions/292058/network-wide-https-its-time |
| 01:33 | <domfarolino> | about time |
| 01:49 | <Domenic> | srsly |
| 08:24 | <annevk> | MikeSmith: Bugzilla spam: https://www.w3.org/Bugs/Public/show_bug.cgi?id=30073 |
| 08:24 | MikeSmith | looks |
| 08:35 | <botie> | noah, at 2017-03-08 05:55 UTC, annevk said: we can reword the IPv6 serializer to make it clearer |
| 08:36 | <noah> | annevk: 👍🏻 |
| 08:37 | <annevk> | noah: if you want, you can even try to do so yourself |
| 08:37 | <noah> | wondering why https://github.com/jsdom/whatwg-url uses https://github.com/Sebmaster/tr46.js as opposed to https://github.com/jcranmer/idna-uts46 |
| 08:38 | <noah> | if i can make sense of it yeah |
| 08:44 | <MikeSmith> | Subresource Integrity getting implemented in WebKit https://bugs.webkit.org/show_bug.cgi?id=148363 patch under review |
| 08:45 | <noah> | Sebmaster: Domenic: maybe you know the answer?☝🏻 |
| 14:04 | <wanderview> | Domenic: thanks... so Unloaded is not a thing anymore |
| 14:11 | <annevk> | wanderview: would appreciate input on https://github.com/whatwg/fetch/pull/502 |
| 14:15 | <wanderview> | annevk: I'm sorry, but I don't have an opinion on that... seems fine either way |
| 14:15 | <wanderview> | annevk: maybe mcmanus or someone on his team would have an opinion |
| 14:15 | <annevk> | wanderview: I mostly want to know whether we can change |
| 14:16 | <annevk> | wanderview: I wish it was easier to get input from them |
| 14:16 | <annevk> | anyway, thanks |
| 14:16 | <wanderview> | annevk: I mean, we can do anything we want... but I doubt we would make a change immediately |
| 14:16 | <wanderview> | annevk: sorry, I'm really slammed with this deadline |
| 14:16 | <annevk> | wanderview: I found a bug in https://github.com/w3c/web-platform-tests/blob/master/XMLHttpRequest/open-url-redirected-worker-origin.htm and will post a patch to WPT |
| 14:17 | <wanderview> | annevk: oh? |
| 14:17 | <annevk> | wanderview: I changed a whole lot of XHR infrastructure to be more sensitive to casing |
| 14:17 | <annevk> | wanderview: so this test ends up failing because it expects lowercase header names |
| 14:18 | <wanderview> | ah, ok |
| 14:18 | <wanderview> | sounds good |
| 14:18 | <wanderview> | annevk: I was worried the referer behavior was wrong or something |
| 14:19 | <wanderview> | annevk: I copied most of that test from another test (like all good tests are created) |
| 19:31 | <noah> | annevk: maybe you know? wondering why github.com/jsdom/whatwg-url uses github.com/Sebmaster/tr46.js as opposed to github.com/jcranmer/idna-uts46 |
| 19:33 | <noah> | i guess idna-uts46 is older... but tr46.js has this worrisome issue https://github.com/Sebmaster/tr46.js/issues/6 |
| 19:34 | <noah> | is there a decent implementation of uts46 in any language? :-| |
| 19:36 | <Sebmaster> | noah: that issue doesn't really count. The unicode tests are... subpar to say the least. A lot of the tests do not apply to uts46 |
| 19:38 | <noah> | Sebmaster: oh? |
| 19:39 | <Sebmaster> | Yeah. It seems there is a single test file for all unicode url standards... which are incompatible with each other sooo |
| 19:39 | <Sebmaster> | Doesn't really make sense |
| 19:39 | <Sebmaster> | Not quite sure why we didn't use that other lib. Might not have found it in time |
| 19:40 | <noah> | you mean IdnaTest.txt i assume, and by "all unicode url standards" do you mean idna2003, idna2008 and uts46? |
| 19:49 | <annevk> | noah: I also found IdnaTest.txt problematic: https://lists.w3.org/Archives/Public/www-archive/2017Jan/0011.html |
| 19:49 | <annevk> | I haven't really started digging yet because I want to hear from implementers |
| 19:49 | <annevk> | And from the UTS46 people |
| 19:51 | <noah> | Sebmaster: annevk: well, i took a look at the first test failure "Web Platform Tests Converting <àא> with type B: AssertionError: toASCII should result in an error", and chromium seems to agree with IdnaTest.txt, not with tr46.js |
| 19:57 | <noah> | annevk: you ran IdnaTest.txt tests across all browsers and found failures and inconsistencies among browsers. disappointing but good to know, thanks for doing that work |
| 22:21 | <zcorpan> | MikeSmith: fyi https://github.com/htacg/tidy-html5/issues/352#issuecomment-285449909 |
| 22:27 | MikeSmith | looks |
| 22:30 | <MikeSmith> | zcorpan: maybe I should make the checker emit a link to the URL spec in the error messages for URL checks? |
| 22:30 | <zcorpan> | MikeSmith: does the checker implement the url spec? |
| 22:31 | <MikeSmith> | to the degree that galimatias does |
| 22:32 | <MikeSmith> | is it wrong in this case? |
| 22:32 | <MikeSmith> | I’m running a fork of galimatias so if it is wrong in any particular case I can just fix it in the fork |
| 22:33 | <MikeSmith> | upstream galimatias is no longer being maintained and there are some places where I know it’s not conforming with the current spec |
| 22:34 | <MikeSmith> | and I have been having discussions with somebody who may end up providing a new implementation that attempts to fully conform to the current spec and who will maintain it to keep up with any changes to the spec |
| 22:34 | <MikeSmith> | but don’t have that in hand yet |
| 22:34 | <MikeSmith> | so for now I just have to patch galimatias if any problems are found |
| 22:35 | <mounir> | dbaron: any chance I can get your feedback on https://github.com/w3c/csswg-drafts/issues/993 ? :) |
| 22:35 | <zcorpan> | i don't know, but was under the impression that galimatias kinda pre-dated whatwg url |
| 22:36 | <MikeSmith> | zcorpan: well is there some problem in this particular case? is <a href=":|"> valid? |
| 22:36 | <MikeSmith> | is there some online conforming parser I can against? |
| 22:37 | <MikeSmith> | I thought annevk maintained one |
| 22:37 | <zcorpan> | MikeSmith: https://a/?| is i think? |
| 22:37 | <zcorpan> | https://quuz.org/url/liveview.html#https://a/?| |
| 22:39 | <zcorpan> | no it's not. https://url.spec.whatwg.org/#url-query-string |
| 22:39 | <MikeSmith> | yeah |
| 22:40 | <MikeSmith> | so I guess quuz.org/url doesn’t show errors for syntax violations |
| 22:40 | <zcorpan> | the code snippet that he posted is an implementation of https://url.spec.whatwg.org/#url-code-points right? |
| 22:40 | <MikeSmith> | yup |
| 22:41 | <MikeSmith> | though btw what I do in the checker is, it uses http://example.com/foo as the base |
| 22:42 | <MikeSmith> | which is arbitrary but it needs a base to parse against |
| 22:44 | <MikeSmith> | https://github.com/validator/validator/blob/master/src/nu/validator/datatype/IriRef.java#L129 |
| 22:45 | <MikeSmith> | anyway as far as tidy goes, the much bigger problem with it is, it’s using an ad-hoc parser that’s not anywhere even close to conforming to the HTML spec |
| 22:45 | <dbaron> | mounir: done |
| 22:48 | <MikeSmith> | zcorpan: hmm it just now occurred to me that I may be able to use jsdom/whatwg-url as the URL parser for the HTML checker |
| 22:49 | <MikeSmith> | zcorpan: by using the Java8 Nashorn stuff to expose it to the checker Java code |
| 22:50 | <MikeSmith> | oh but only if jsdom/whatwg-url emits good errors for syntax violations |
| 22:53 | <Sebmaster> | MikeSmith: it does not tell you what's wrong |
| 22:53 | <Sebmaster> | only that there is (and slightly more detailed if you use private api) |
| 22:53 | <MikeSmith> | Sebmaster: yeah just discovered that from looking at the code :( |
| 22:53 | <zcorpan> | mounir: wonder if we should drop the recommendation about clamping to 24? or try to somehow research what the web compat impact would be for returning lower values |
| 22:54 | <MikeSmith> | Sebmaster: I think it would be useful to a lot of people if it did emit error messages to the console for the parseError = true cases |
| 22:55 | <MikeSmith> | Sebmaster: I thought there was another JS URL parser that did implement error messages |
| 22:55 | <Sebmaster> | console is definitely not an option. saving it in the private api might be, but we're currently trying to just very explicitly do what's in the spec so you can put the text next to the code and it lines up perfectly |
| 22:57 | <MikeSmith> | well a private API would work fine too |
| 22:58 | <MikeSmith> | and I support the design choice of having it explicitly do what’s in the spec so it lines up clearly :) |
| 22:58 | <MikeSmith> | makes it much easier to understand the code |
| 23:01 | <MikeSmith> | Sebmaster: anyway the code for the HTML checker is in Java but Java8 now has this built-in way to use JavaScript code in Java, so if whatwg-url had a way to emit error messages I could (maybe) use it as the URL parser for the HTML checker |
| 23:14 | <Domenic> | I still think the best way to validate URLs is to implement the grammar in the "URL writing" section of the spec |
| 23:14 | <Domenic> | That'll be much easier |
| 23:14 | <Domenic> | https://url.spec.whatwg.org/#url-writing this would take like an hour |
| 23:29 | <mounir> | zcorpan: I can't remember off hand why I campled to 24 but it sounds that it would provide little benefit to give lower values, wouldn't it? |
| 23:29 | <mounir> | zcorpan: though, Blink, I believe, would return 2 for BW devices (at least, I think the color MQ does) |
| 23:29 | <mounir> | I guess maybe 1 :) |
| 23:30 | <zcorpan> | mounir: maybe it was something I suggested ^_^ |
| 23:32 | <mounir> | zcorpan: happy to drop it |
| 23:32 | <mounir> | dbaron: would you be happy with this? |
| 23:33 | <dbaron> | mounir: I'd be ok with allowing <24. |
| 23:40 | <mounir> | zcorpan, dbaron: updated :) |