| 00:20 | <Domenic> | annevk: are you able to own reviewing https://github.com/whatwg/html/pull/3260 ? (inputmode) |
| 00:57 | <Domenic> | annevk: also ping on https://github.com/whatwg/html/pull/3221#issuecomment-347262185 (img decoding="") |
| 04:21 | <annevk> | Domenic: I was planning on reviewing inputmode once the high-level questions are addressed |
| 04:22 | <Domenic> | Yeah, OK, seems like it's on dtapuska's plate for now, just wanted to know if you'd review once he gets back to it or if I should feel responsible :) |
| 04:24 | <annevk> | Domenic: I guess the decoding thread concluded in a follow-up issue for possibly a third new feature, but not in changes to the decoding attribute; that should probably be stated though and then an issue raised. Then on Monday or Tuesday we can merge imo |
| 04:25 | <annevk> | Domenic: I’m happy to take on inputmode |
| 04:26 | <Domenic> | Yay. I'm excited about inputmode (and autocapitalize/autocorrect); they're long overdue updates to make the spec match reality |
| 04:41 | <annevk> | Domenic: that MIME type parser patch looks cool (will get to GitHub a couple hours from now) |
| 04:42 | <annevk> | Domenic: interesting that you went with a tearoff for parameters |
| 04:43 | <Domenic> | Yeah, it seemed a bit nicer, like searchParams |
| 10:28 | <Mek> | annevk: the current file-api spec has a ton of informative background/discussion around how they ended up with this particular format for blob URLs. While interesting background (maybe), it doesn't seem to add much. I'm tempted to just rip most of that out, does that sound sensible? |
| 10:29 | <Mek> | Also of course all the informative text around resolving/parsing/fetching that is now superseded by the fetch and url specs seems to do more harm then good |
| 10:29 | <annevk> | Mek: yeah |
| 10:30 | <annevk> | Mek: do it as a PR though so folks have a notice of a day or so |
| 10:31 | <Mek> | yeah, definitely don't want to do any major changes without some amount of review |
| 10:32 | <annevk> | Mek: FWIW, most WHATWG stuff basically protects the master branch and requires (reviewed) PRs |
| 10:33 | <annevk> | tooling is such a wonderful thing |
| 11:45 | <KiChjang> | quesiton about valid date/month strings |
| 11:45 | <KiChjang> | https://html.spec.whatwg.org/multipage/common-microsyntaxes.html#valid-date-string |
| 11:46 | <KiChjang> | so a date string is considered valid if it consists of the components outlined by that part of the spec |
| 11:46 | <KiChjang> | is it valid ONLY if it contains those components? |
| 11:46 | <KiChjang> | in other words, would "2014-01-01-1" be valid date string? |
| 11:53 | <annevk> | KiChjang: how could that be valid? |
| 11:54 | <nox> | annevk: KiChjang wants the spec to say "consists ONLY of the components …". |
| 11:55 | <annevk> | I think that would require rewording a lot of factual statements which I'm not sure would be beneficial |
| 11:55 | <KiChjang> | annevk, yeah, because i'm reading it as "as long as a string consists of these components, then it's a valid date string" |
| 11:56 | <annevk> | "A URL's port is a 16-bit unsigned integer" vs "A URL's port is ONLY a 16-bit unsigned integer" |
| 11:56 | <nox> | I've never seen uses of 'consist of' to refer only to a subset of the parts. |
| 11:56 | <nox> | If it refers to a subset, you usually read "mainly consist of" or something similar. |
| 11:58 | <annevk> | I could see rephrasing these though |
| 11:58 | <nox> | 'Attributes are placed inside the start tag, and consist of a name and a value, separated by an "=" character.' |
| 11:58 | <annevk> | Just make it "A valid month string is X followed by Y followed by Z" |
| 11:58 | <annevk> | There's no need for these variables in the definition and such |
| 11:58 | <KiChjang> | annevk, i'm thinking of it in terms of exhaustiveness |
| 11:58 | <KiChjang> | because it seems to me that it allows for additiona characters at the end |
| 11:59 | <nox> | KiChjang: Why? |
| 11:59 | <nox> | Does the thing I pasted let you think that 'a="b"c' is an attribute too? |
| 11:59 | <annevk> | KiChjang: I don't think that's true with the current language (though I'll note again I'd support simplifying it) |
| 12:01 | <KiChjang> | nox: yes, because a is the name, and "b"c is the value |
| 12:02 | <nox> | Not sure I understand what you mean. |
| 12:03 | <nox> | Looking at https://www.google.fr/search?q=inurl:https://html.spec.whatwg.org/multipage/+%22consist+of%22 I feel like you don't interpret 'consist of' correctly. |
| 13:47 | <annevk> | Domenic: that code coverage thing is so great |
| 14:05 | <Domenic> | ^_^ |
| 14:19 | <annevk> | Domenic: ideas on how to deal with the code points? Some contexts cannot deal with non-latin1. Should we ignore those tests in the respective harness or encode that in the test somehow? |
| 14:20 | <Domenic> | Seems important to test... what contexts, and what does "not deal with" mean? |
| 14:20 | <Domenic> | The parser will fail for such code points anyway, right? |
| 14:21 | <annevk> | Domenic: consider the Content-Type header |
| 14:21 | <annevk> | Domenic: it takes 0x00 to 0xFF |
| 14:21 | <annevk> | Domenic: so if you pass it U+0100 you cannot really express that |
| 14:22 | <annevk> | Domenic: you could UTF-8 encode it, but then you're testing something else |
| 14:22 | <annevk> | Domenic: the parser will ignore the parameters or fail if part of type/subtype |
| 14:24 | <Domenic> | So why not test it just like any other invalid code point though |
| 14:24 | <Domenic> | Oh I see |
| 14:24 | <annevk> | Domenic: strings <> bytes |
| 14:24 | <Domenic> | This is in bytes-only contexts |
| 14:24 | <annevk> | hai |
| 14:24 | <Domenic> | Lemme look at the test code, since I don't think we tested any APIs that use ArrayBuffers... |
| 14:25 | <annevk> | Note that Request/Response are such a context too |
| 14:25 | <annevk> | Due to ByteString |
| 14:25 | <Domenic> | I see, this is mainly about what happens on the Python side hmm |
| 14:25 | <annevk> | Blob/File are not though and I'm not convinced MIMEType should use ByteString |
| 14:26 | <Domenic> | Why not? |
| 14:26 | <Domenic> | I guess Blob/File are not for compat reasons |
| 14:26 | <Domenic> | But new APIs should, I'd think |
| 14:26 | <annevk> | Domenic: MIMEType would end up with lots of double conversion |
| 14:27 | <Domenic> | Only on a spec level |
| 14:27 | <annevk> | Domenic: unless someone redefines the parser to operate on byte sequences, but then it gets weird for non byte input |
| 14:27 | <Domenic> | Don't you have a byte parser? |
| 14:27 | <Domenic> | It just isomorphic encodes |
| 14:27 | <annevk> | Domenic: I guess we can do it and hope impl are better (and hope Infra at some point abstracts) |
| 14:28 | <Domenic> | I guess MIMEType would throw anyway if you gave it invalid code points |
| 14:28 | <annevk> | Domenic: yeah, I think it should |
| 14:28 | <Domenic> | So it doesn't need to use ByteString, since that just moves most of the checks, but not all, to the IDL layer |
| 14:28 | <annevk> | Domenic: and since I get to do it most likely it would just throw TypeError |
| 14:28 | <Domenic> | Anyway back to the question |
| 14:29 | <annevk> | So can't use navigable as a distinguisher due to Request/Response |
| 14:29 | <annevk> | The best thing I can come up with is that the harness needs to filter |
| 14:29 | <Domenic> | Hmm yeah I guess that's better than adding it to the data file |
| 14:30 | <annevk> | For Request/Response we'd also want to add a filter that it throws for 0x00 and 0x0C/0x0A |
| 14:30 | <annevk> | Same for Content-Type, but there's some additional bytes that won't work due to WPT limitations |
| 14:30 | <Domenic> | Seems reasonable |
| 14:31 | <annevk> | Okay, so I'll go with that and attempt at some documentation in the README |
| 14:32 | <Domenic> | I still feel like we should be testing what happens when you send invalid/weird Content-Type headers to servers... but I guess that's really just a test of your server-side framework and whether it does any canonicalization... |
| 14:41 | <annevk> | Domenic: there are such tests |
| 14:41 | <annevk> | Domenic: did you look at the other PRs? https://github.com/w3c/web-platform-tests/pull/8422 |
| 14:42 | <annevk> | Domenic: that sends e.g. "charset=ascii" to the server and verifies that the browser doesn't change it |
| 14:42 | <Domenic> | Yeah, I guess that's testing that wptserve doesn't do any canonicalization |
| 14:52 | <ecobos> | https://drafts.csswg.org/ seems down for me? |
| 15:05 | <ecobos> | works now, shrug |
| 16:15 | <annevk> | Domenic: looks like generated tests are not getting done today |
| 16:16 | <annevk> | Domenic: but I've some Python locally that is going in the right direction |
| 16:16 | <annevk> | Domenic: exhaustive means a thousand tests or so though; not sure if we want browsers to run all of those all the time... |
| 16:22 | <annevk> | Also, the next format I come up with will have !/! or +/- or some such as MIME type |
| 16:22 | <annevk> | Does Bitcoin have some kind of format? $/$ is valid... |
| 16:25 | <wanderview> | "Change quote style in lipfuzz example" |
| 16:25 | wanderview | wonders what "lipfuzz" is... |
| 17:27 | <Domenic> | wanderview: see if you get it after reading the example: https://streams.spec.whatwg.org/#example-ts-lipfuzz |
| 17:37 | <annevk> | Domenic: script I have locally generates 885 tests |
| 17:37 | <annevk> | Domenic: gonna try integrate it later and see what blows up, but have to do some other things for a bit |
| 17:46 | <hober> | how does one rename a user account on the wiki? |
| 17:48 | <annevk> | GPHemsley: Krinkle: any idea how to rename accounts on MediaWiki? |
| 17:49 | <annevk> | See question by hober above |
| 17:59 | <hober> | i think maybe it requires this extension: https://www.mediawiki.org/wiki/Extension:Renameuser |
| 18:02 | <annevk> | hober: ah, it might be best to email GPHemsley directly then |
| 18:02 | <annevk> | Not entirely sure when he's online |
| 18:02 | <hober> | k |
| 18:02 | <hober> | thanks |
| 18:34 | <Krinkle> | annevk: Yep, Renameuser it is. It's bundled by default in most distros, so might already be there. |
| 18:34 | <Krinkle> | or not :) - https://wiki.whatwg.org/wiki/Special:Version |
| 18:34 | <annevk> | Yeah, alas |
| 18:49 | <wanderview> | JakeA: worker script loads don't get a manual redirect mode, right? we only do that for windows to support their weird redirect logic? |
| 18:50 | <JakeA> | wanderview: I thought redirects weren't allowed. Anyway, in India, will catch up with messages next week. |
| 18:51 | <wanderview> | JakeA: ah, ok... I believe same-origin redirects are legal for worker scripts... good night |
| 18:51 | <wanderview> | service worker scripts are not allowed to redirect, but dedicated workers can |
| 19:01 | <annevk> | Yup, shared same as dedicated |
| 19:21 | <tobie> | TabAtkins: is https://api.csswg.org/bikeshed/ having issues? |
| 19:22 | <TabAtkins> | Dunno, don't use it. It seems to load correctly, at least. What problem are you having? |
| 19:22 | <tobie> | I'm getting a 400 for this: https://api.csswg.org/bikeshed/?url=https%3A%2F%2Fraw.githubusercontent.com%2Ftobie%2Fwebidl%2F79a0f335ea4420a9092a27fdd10f349f35e64a3e%2Findex.bs&md-warning=not%20ready |
| 19:23 | <TabAtkins> | I'll ping plinss, he's the maintainer of that server. |
| 19:23 | <tobie> | TabAtkins: I probably did something silly |
| 19:23 | <tobie> | TabAtkins: cool thanks |
| 19:24 | <wanderview> | html.spec.whatwg.org is down? |
| 19:27 | <wanderview> | annevk: you seeing that? ^^^ |
| 19:28 | <wanderview> | stuck on TLS handshake... |
| 19:32 | <annevk> | wanderview: hmm, foolip, MikeSmith ^^ |
| 19:33 | <TabAtkins> | tobie: plinss reports it's an issue on his side, he'll work on it |
| 19:33 | <tobie> | TabAtkins: oh, cool :) ty |
| 19:45 | <wanderview> | JakeA: for your reading next week: https://github.com/w3c/ServiceWorker/issues/1239 |
| 20:38 | <TabAtkins> | tobie: Ahahahaha, I read your comment in #css and thought it was from plinss. The error was def on your side, sorry. ^_^ |
| 20:39 | <tobie> | TabAtkins: I thought so |
| 20:39 | <tobie> | TabAtkins: seems it's an update to bikeshed that's causing an error to something that was working fine before |
| 20:40 | <TabAtkins> | I'll check it out, I've been working on indents lately (fixing some bugs). |
| 20:40 | <tobie> | TabAtkins: looks like it's related |
| 20:41 | <TabAtkins> | Yeah, I checked the error message. ^_^ |
| 21:05 | <Domenic> | wanderview: works for me, plus http://downforeveryoneorjustme.com/html.spec.whatwg.org , but we are switching some hosting around, so it could be DNS fun times... |
| 21:06 | <wanderview> | Domenic: wfm now |