| 08:40 | <annevk> | JakeA: in case you forgot about https://github.com/whatwg/fetch/pull/435 here's a friendly reminder (I'm in no hurry though, just noticed it's likely after your break) |
| 09:35 | <JakeA> | annevk: cheers. Hadn't forgotten, but yeah, will start this today. Last time I looked Chrome was crashing on the fetch tests, so might end up down a rabbit hole |
| 09:36 | <annevk> | Well, as I said, I don't think we're in a particular rush with that refactoring, so up to you |
| 09:57 | <annevk> | jgraham: is there any H/2 talk with regards to WPT? |
| 09:58 | <annevk> | jgraham: and also, is there a way to enforce H/1 for certain tests? |
| 10:19 | <jgraham> | annevk: No and therefore no. I mean everything enforce http/1.1 at the moment; if you aren't running through wptserve it's an unsupported configuration |
| 10:19 | <annevk> | jgraham: wptserve is used for WebSocket too? |
| 10:20 | <jgraham> | Oh, no |
| 10:20 | <annevk> | jgraham: or to ask differently, tracking issues should be filed there? |
| 10:20 | <jgraham> | pywebsocket is used then |
| 10:20 | <annevk> | I see |
| 10:20 | <annevk> | I guess when I end up writing those tests I can say they assume H/1 |
| 10:20 | <jgraham> | If http/2 is required I guess I should add that to my list of "reasons to spend more time on web-platform-tests this year" |
| 10:21 | <jgraham> | That is, if there are things that can't be tested or might work differently with http/2 |
| 10:21 | <annevk> | jgraham: it would be good for Fetch at least to test H/2 framing and such |
| 10:21 | <jgraham> | OK. There is a bug somewhere, right? |
| 10:22 | <jgraham> | Can you add a comment if there isn't one already |
| 10:22 | <annevk> | jgraham: I don't know, I just got curious |
| 10:22 | <annevk> | jgraham: there is a bug about sending responses earlier |
| 10:22 | <annevk> | jgraham: should I file a bug against wptserve? |
| 10:23 | <jgraham> | annevk: Sure |
| 10:24 | <Ms2ger> | annevk, hey, you know a few things about incumbent globals, right? |
| 10:25 | <annevk> | Ms2ger: don't use m? |
| 10:26 | <annevk> | Ms2ger: the main thing I know about incumbent globals is that they're not a shared concept across all browsers |
| 10:26 | <annevk> | Ms2ger: main important thing, that is |
| 10:28 | <annevk> | jgraham: filed https://github.com/w3c/wptserve/issues/110 |
| 10:29 | <annevk> | jgraham: https://github.com/w3c/wptserve/issues/80 is the other issue, with early responses |
| 10:29 | <annevk> | jgraham: that would be more interesting to have I think since it enables completely new scenarios and bugs |
| 10:30 | <Ms2ger> | It seems like https://html.spec.whatwg.org/multipage/webappapis.html#the-event-handler-processing-algorithm uses `callback` as a WebIDL callback function (which has an incumbent global stored as the "callback context"), but it's created as a JS function, which doesn't have that |
| 10:30 | <annevk> | jgraham: basically being able to send a response from the server the moment the server has all the request headers, not necessarily the request body |
| 10:32 | <annevk> | Ms2ger: because of step 1? |
| 10:32 | <Ms2ger> | Yeah, https://html.spec.whatwg.org/multipage/webappapis.html#getting-the-current-value-of-the-event-handler just does FunctionCreate |
| 10:33 | <annevk> | Ms2ger: new issue đŸ˜Ÿ |
| 10:34 | <annevk> | Ms2ger: that should indeed some some kind of IDLFunctionCreate |
| 10:34 | <Ms2ger> | On its way |
| 10:34 | <Ms2ger> | The annoying thing is that it's called without JS on the stack |
| 11:53 | <JakeA> | annevk: I'm getting "updating and loading test manifest; this may take several minutes" on web-platform-tests. It doesn't seem to ever finish |
| 11:54 | <JakeA> | I'm also getting a ManifestVersionMismatch error in the console |
| 11:54 | <JakeA> | (server console that is) |
| 11:56 | <annevk> | JakeA: what are you trying to do? |
| 11:56 | <JakeA> | annevk: run the fetch tests |
| 11:57 | <JakeA> | annevk: I visit http://web-platform.test:8000/tools/runner/index.html and get that error |
| 11:57 | <annevk> | JakeA: I see, you can also go to e.g. http://web-platform.test:8000/fetch/api/headers/headers-errors.html directly |
| 11:57 | <annevk> | JakeA: that's what I usually do |
| 11:57 | <jgraham> | JakeA: Delete your MANIFEST.json |
| 11:57 | <annevk> | JakeA: jgraham might be able to help with questions regarding the runner |
| 11:57 | <annevk> | There you go |
| 11:57 | <jgraham> | We changed the manifest format and it probably isn't intelligent enough to just regenerate it in the new format |
| 11:58 | annevk | hasn't used the runner |
| 11:58 | <jgraham> | Yeah, the runner isn't great |
| 11:59 | <JakeA> | jgraham: where's MANIFEST.json? |
| 11:59 | <JakeA> | oh top dir |
| 11:59 | <JakeA> | sorry |
| 12:00 | <JakeA> | jgraham: thanks, that's working now |
| 12:03 | <jgraham> | Apologies for the inconvenience |
| 12:05 | <MikeSmith> | ah yeah |
| 12:05 | <MikeSmith> | Cindy ran into the same problem and pinged me about it |
| 12:05 | <MikeSmith> | told her the same thing |
| 12:05 | <MikeSmith> | rm MANIFEST.json && ./manifest |
| 12:06 | <jgraham> | We can probably make it happen by magic, although if the rebuild takes too long the request might time out |
| 12:06 | <MikeSmith> | yeah |
| 12:41 | <JakeA> | jgraham: is there a process for running the tests over https? |
| 13:00 | <JakeA> | jgraham: figured it out. Filed https://github.com/w3c/web-platform-tests/issues/4514 as a reminder to document it |
| 13:11 | <annevk> | Why does wpt-stability-bot report results in seemingly random order? |
| 13:11 | <gsnedders> | annevk: Python hash order, maybe? |
| 13:11 | <gsnedders> | annevk: feel free to file a bug, tho |
| 13:12 | <annevk> | gsnedders: can you point me to the code perhaps? |
| 13:12 | <annevk> | gsnedders: maybe I can propose a change |
| 13:12 | <gsnedders> | /check_stability.py, IIRC |
| 13:12 | <annevk> | https://github.com/wpt-stability-bot should probably mention where you can patch it |
| 13:13 | <gsnedders> | I mean it could also be somewhere in wptrunner |
| 13:13 | <gsnedders> | annevk: idk how has access to that, maybe only jgraham |
| 13:14 | <gsnedders> | class LogHandler is where it all goes wrong |
| 13:14 | <gsnedders> | though replacing those with ordered dicts is harder than I'd like |
| 13:15 | <annevk> | Yeah, was just looking at that |
| 13:15 | <annevk> | I'm going to file an issue for now and get back to IDNA |
| 13:36 | <jochen__> | any suggestions what name to use to refer to an "inline style declaration" |
| 13:36 | <jochen__> | as opposed to a stylesheet |
| 13:37 | <jochen__> | i want to say something "if an url() is part of an inline style, then do this" |
| 13:46 | <annevk> | jochen__: it sounds like that requires a hook in the CSS parser or some such |
| 13:47 | <annevk> | jochen__: so probably best to ask the CSS WG for such a hook |
| 13:47 | <annevk> | jochen__: unless you're happy with your text not being the long term solution, in which case you can do whatever |
| 13:47 | <annevk> | (within reason) |
| 14:37 | <jgraham> | MikeSmith, JakeA: I think the manifest version mismatch problem is fixed now |
| 14:41 | <MikeSmith> | jgraham: super, thanks |
| 14:41 | <MikeSmith> | will let Cindy know too |
| 14:41 | <MikeSmith> | annevk: spaces around em dash? |
| 14:43 | <annevk> | MikeSmith: seems to be the norm |
| 14:43 | <MikeSmith> | really |
| 14:43 | <annevk> | I personally think it reads better too, but I know it's sometimes frowned upon too |
| 14:44 | <MikeSmith> | it’s not the norm in any style guide I have ever seen, nor in pretty much any print newspaper or magazine or book |
| 14:45 | <MikeSmith> | but that said I can live it as long as we do it consistently |
| 14:46 | <MikeSmith> | anything is better than continuing to instead do -- forever |
| 14:47 | <gsnedders> | two hyphens is normally en-dash |
| 14:47 | <gsnedders> | but yeah, I agree with annevk that it reads better IMO, but AFAIK pretty much every style guide ever says no spaces |
| 14:48 | <jgraham> | I really will never understand—and believe me I have tried—why style guides think no space is a good idea |
| 14:49 | <annevk> | I don't think any WHATWG Standard avoids spaces |
| 14:50 | <MikeSmith> | y’all sound like you probably think two spaces after a period reads better too |
| 14:51 | <jgraham> | I hope not |
| 14:51 | <annevk> | Nooo, those are bad |
| 14:52 | <annevk> | And trimmed by CSS unless you use so rather pointless anyway |
| 14:53 | <annevk> | If you have a string with that reads "\u1234†" how do you convert the \u1234 to a code point in the easiest way with Python? |
| 14:53 | <annevk> | Do I need my own tokenizer of sorts or is there a simple utility? |
| 14:58 | <MikeSmith> | now that is something that jgraham and gsnedders definitely know more about than I do |
| 14:59 | <jgraham> | You have a literal python escape in a string? |
| 14:59 | <jgraham> | In [2]: "\\u1234".decode("unicode-escape") |
| 14:59 | <jgraham> | Out[2]: u'\u1234 |
| 15:04 | <annevk> | jgraham: cool |
| 15:18 | wanderview | considers staying an extra day or two after SW meeting in tokyo... |
| 15:21 | <JakeA> | jgraham: cheers! |
| 15:24 | <wanderview> | oooh... JakeA is writing WPT tests? |
| 15:35 | <annevk> | jgraham: I guess they're not literal Python escapes after all, since they can be up to six digits |
| 15:43 | <jgraham> | annevk: Ah, python ones are like "\\U00101234".decode("unicode-escape") for non-BMP |
| 15:44 | <jgraham> | Seems like they got scared that someone would sneak in some more codepoints |
| 16:08 | <MikeSmith> | gsnedders: the tree at https://validator.w3.org/nu/parsetree/?parser=html5&content=%3C%21DOCTYPE+html%3E%3Cnoscript%3E%3Cimg+src%3Dfoo%3E%3C%2Fnoscript%3E&submit=Print+Tree is not correct, right? |
| 16:16 | <MikeSmith> | that is, it parses <!DOCTYPE html><noscript><img src=foo></noscript> into <html><head><noscript></noscript></head><body><img src=foo>... |
| 16:16 | <MikeSmith> | but browsers do not seem to do that that |
| 16:18 | <MikeSmith> | zcorpan: ⬆ |
| 16:19 | <zcorpan> | MikeSmith: scripting disabled? |
| 16:19 | <MikeSmith> | ah |
| 16:19 | <MikeSmith> | yeah I guess that’s the difference |
| 16:20 | <MikeSmith> | vnu parser runs in the HTML checker with scripting disabled |
| 17:07 | <annevk> | jgraham: turned out they were of the \uXXXX type after all, but that doesn't really work with Python if the string contains those and non-ASCII code points |
| 17:08 | <jgraham> | What doesn't work? |
| 17:10 | <annevk> | jgraham: it turned a legitimate \u00df into \u00XX\u00XX where those XX were the utf-8 byte sequence for U+00DF |
| 17:11 | <annevk> | jgraham: I then tried to run decode("utf-8") first and then run decode("escape-string"), but yielded similar bad results |
| 17:11 | <annevk> | A custom method did the trick however... |
| 17:12 | <annevk> | I'm guessing I should really be using Python 3.0 to avoid this, but then that doesn't come by default on the OS |
| 17:12 | <jgraham> | In [8]: "\\u00df".decode("unicode-escape") |
| 17:12 | <jgraham> | Out[8]: u'\xdf' |
| 17:12 | <jgraham> | In [9]: "\xdf".decode("unicode-escape") |
| 17:12 | <jgraham> | Out[9]: u'\xdf' |
| 17:14 | <annevk> | jgraham: but the input is something like "\\u1234 \u00DF" (so escapes and actual code points) |
| 17:14 | <annevk> | Anyway, I wrote a custom thing |
| 17:15 | <annevk> | jgraham: if you want to review or improve upon my way, it's in https://github.com/w3c/web-platform-tests/pull/4504 as IdnaTest.py |
| 17:17 | <jgraham> | annevk: Oh I see. If you already have a unicode string, running .decode() on it will probably cause badness (attempting to encode to ascii first or something) |
| 17:24 | <Domenic> | Wait when in the Tokyo service workers meeting? |
| 17:26 | <annevk> | Domenic: it's 3-4 April, JakeA can give you the details |
| 17:26 | <Domenic> | Hmm OK |
| 17:26 | <Domenic> | foolip is out there all of March and I am scheduling my trip to probably overlap with his |
| 17:26 | <Domenic> | Maybe I should go for end of March / beginning of April for maximum overlap |
| 17:27 | <annevk> | We're likely moving house, so no trips |
| 18:47 | <JakeA> | wanderview: I know right! Dangerous times. Hoping to have something to PR tomorrow. Just getting up to speed today & got sidetracked a little |
| 18:47 | <JakeA> | But seems like something I should be doing with all spec things |
| 18:47 | <JakeA> | Domenic: you're more than welcome to the SW meeting. Happy for streams to be part of that too. |