| 05:35 | <annevk> | MikeSmith: guess we should add a note |
| 05:36 | <annevk> | MikeSmith: the header and method production allow for * |
| 05:39 | <MikeSmith> | yeah to be clear, it’s not a problem for implementors |
| 05:39 | <MikeSmith> | instead just for developers/authors reading the spec |
| 05:40 | <MikeSmith> | the root problem for developers/authors is that from reading the spec, it’s not clear they can use * in Access-Control-Allow-Headers to mean “any header name” |
| 05:41 | <MikeSmith> | anyway I will make time to write up a PR that adds a note |
| 05:49 | <annevk> | The ABNF is mostly for implementers but sure |
| 05:51 | <MikeSmith> | yeah |
| 05:55 | <MikeSmith> | maybe making it clear to developers/authors is as simple as changing “For `Access-Control-Expose-Headers`, `Access-Control-Allow-Methods`, and `Access-Control-Allow-Headers` response headers the value `*` counts as a wildcard” to “For `Access-Control-Expose-Headers`, `Access-Control-Allow-Methods`, and `Access-Control-Allow-Headers` response headers, you can use the value `*` as a wildcard |
| 05:55 | <MikeSmith> | (to mean "any header name" or "any method name")” |
| 06:00 | <annevk> | I’d have to read the CORS section again |
| 07:05 | <annevk> | foolip: https://github.com/whatwg/dom/issues/410 |
| 07:14 | <foolip> | annevk: I have it pinned in my inbox, but won't be back at work until Tuesday |
| 07:15 | <annevk> | foolip: oh sorry, I did see you were away yesterday and forgot again |
| 07:15 | <annevk> | foolip: enjoy things |
| 08:12 | <annevk> | Domenic: can you review https://github.com/w3c/web-platform-tests/pull/9967 too? |
| 08:12 | <Domenic> | foolip are IDL updates automated yet? |
| 08:12 | <annevk> | I don't think so, but note that it does more than just updating the IDL |
| 08:13 | <annevk> | Also, he's on vacation |
| 08:14 | <Domenic> | Fair |
| 08:14 | <foolip> | Domenic: PRs aren't auto-created yet, but lukebjerring is working through all of interfaces/ to get them in sync to enable just that |
| 08:14 | <foolip> | Domenic: the ones with some boilerplate at the top are verbatim copies now |
| 08:14 | <Domenic> | Ah OK cool |
| 09:21 | <Domenic> | annevk: heading on vacation in like 20 minutes, but will try to get through some reviews and bug filing and stuff... |
| 09:21 | <annevk> | Domenic: aah enjoy all the great food there |
| 09:22 | <annevk> | Domenic: you got a week or a couple of weeks? |
| 09:22 | <Domenic> | Two |
| 09:24 | <annevk> | Domenic: I think WebKit/Chrome have contenteditable=plaintext |
| 09:24 | <annevk> | Domenic: at least internally |
| 09:25 | <Domenic> | Huh, I thought that was a proposal from the editing folks that browsers never implemented. |
| 09:25 | <annevk> | Hmm, now I'm starting to doubt, oh well, in any event, we shouldn't have multiple cursor/selection models |
| 09:27 | <annevk> | Nah I was right: https://cs.chromium.org/chromium/src/third_party/WebKit/Source/core/html/HTMLElement.cpp?type=cs&q=contenteditable+plaintext&sq=package:chromium&l=1232 |
| 09:34 | <Domenic> | I mean, we might have one model, but with the Range/Selection API just upconverting a cursor into an empty selection. |
| 09:36 | <annevk> | Domenic: but the <textarea> API seems to do the same |
| 09:36 | <annevk> | Domenic: e.g., for selectionStart, if there's no selection, you get the cursor position |
| 09:36 | <annevk> | Domenic: if we instead always had a selection, there wouldn't be a need to branch |
| 09:37 | <Domenic> | I think partly it's just weird to say that the user's selected some text, but they have actually selected no text |
| 09:37 | <Domenic> | But as I said in the new issue, I haven't dug into all the implications of something "being a selection" vs. being a text entry cursor |
| 11:39 | <hsivonen> | https://www.w3.org/TR/japanese-xml/ is a weird doc. I talks a lot about unconvertional x- labels and then proceeds to say UTF-8 or UTF-16 as a "should" anyway |
| 11:40 | <hsivonen> | *unconventional |
| 11:41 | <hsivonen> | it looks like a really long way to say that you "should" use what XML Processors "must" be able to ingest |
| 13:22 | <annevk> | hsivonen: how did you end up there? |
| 16:18 | <annevk> | I wish we had done Infra years ago |
| 16:18 | <annevk> | Working on https://github.com/whatwg/dom/pull/609 it clarifies so many things |
| 17:39 | <TabAtkins> | Yeah, Infra's so good. |
| 20:44 | <jsbell> | Adding a global idlharness test for webaudio. Oops, need to pull in DOM for Event/EventListener. Oops, and HTML for EventTarget and HTMLMediaElement (at least that last one makes sense). And oops, HTML needs CSSOM for LinkStyle... *sigh* |
| 20:45 | <gsnedders> | if only someone wrote something to do dependency resolution :) |
| 20:46 | <jsbell> | gsnedders: ooh, should I interpret that as: you already did so? |
| 20:46 | <jsbell> | or just on the todo list? |
| 20:46 | <gsnedders> | nah, I didn't |
| 20:47 | <gsnedders> | but it would be nice to have |