| 07:13 | <annevk> | MikeSmith: so I just did it as well, it seems a little weird that the option that we haven't enabled (and creates a merge commit) is still selected by default |
| 07:14 | <annevk> | MikeSmith: probably something GitHub will fix and I'm not the first to notice I guess |
| 07:15 | <MikeSmith> | yeah |
| 07:15 | <MikeSmith> | I ran into that too and reckoned the same thing |
| 07:16 | <MikeSmith> | minor wrinkle that I guess they will get ironed out soon |
| 08:10 | <annevk> | TabAtkins: another issue that's been awaiting a reply from you: https://www.w3.org/Bugs/Public/show_bug.cgi?id=23893 |
| 08:10 | <annevk> | TabAtkins: there's quite a few, perhaps you should schedule some time to work on HTML rendering 😊 |
| 10:48 | <annevk> | What was the way to become op on this channel again? |
| 11:53 | <annevk> | hallvors: I don't think https://github.com/w3c/clipboard-apis/issues/26 can be left to them |
| 11:53 | <annevk> | hallvors: in particular, I believe Michiel works on the W3C HTML fork and that's unlikely to be actively maintained for the long term |
| 11:54 | <annevk> | Heck, it isn't even actively maintained now |
| 11:54 | <hallvors> | annevk: it's more in Selection or Editing land than in HTML though |
| 11:54 | <annevk> | hallvors: focus isn't |
| 11:54 | <annevk> | hallvors: and Clipboard isn't either, last I looked |
| 11:55 | <hallvors> | Not? I don't see any particular requirements I need to follow up that don't seem to be better spec'ed as Editing requirements.. |
| 11:55 | <annevk> | Sorry, DataTransfer |
| 11:55 | <hallvors> | To clarify: I'm not talking about the existing state of things |
| 11:55 | <annevk> | hallvors: e.g. the bits around focus transfer is very much a thing nothing but HTML defines |
| 11:55 | <hallvors> | but more conceptually what belongs where |
| 11:56 | <annevk> | hallvors: I'm having a hard time believing that the focus stuff can migrate from HTML to elsewhere anytime soon |
| 11:56 | <hallvors> | why should the Clipboard API spec have to deal with focus transfer stuff? |
| 11:57 | <annevk> | hallvors: "I have one requirement about focus (as far as I can remember) which is if JS during paste event processing moves focus, the pasting must target the control that gained focus." |
| 11:57 | <annevk> | hallvors: afaict that requires using some kind of hook to clearly indicate what control you're talking about |
| 11:58 | <hallvors> | hm.. crap, why doesn't ReSpec generate a ToC for the spec now?? |
| 11:59 | <hallvors> | OK, now it did |
| 11:59 | <hallvors> | just slow.. |
| 11:59 | <hallvors> | What it says about focus is this one sentence: https://w3c.github.io/clipboard-apis/#event-listeners-that-modify-selection-or-focus |
| 12:00 | <annevk> | hallvors: that link doesn't work |
| 12:00 | <annevk> | But I'm also not sure why it matters that it's a single sentence |
| 12:00 | <annevk> | If it's normative it should be crystal clear how it fits into the bigger picture |
| 12:01 | <hallvors> | because Respec is weird now.. .-p so this needs to hook into some definitions of Focus and Selection to be useful? |
| 12:01 | <hallvors> | (just search for focus, you'll find it fast) |
| 12:04 | <annevk> | hallvors: yeah, all occurrences of focus require some link |
| 12:04 | <hallvors> | annevk: could you add some specific suggestions for that paragraph to issue 26? |
| 12:04 | <annevk> | hallvors: I don't really have good suggestions at the moment, only that we'd want to define it |
| 12:04 | <annevk> | hallvors: and once we do "If the event listener modifies the selection or focus, the clipboard action must be completed on the modified selection." can probably be removed (or turned into a note) since it would follow from the requirements |
| 12:05 | <annevk> | hallvors: whenever you have something out-of-band like that requiring something, it's a good idea to figure out how you can turn it into a note, since it's likely some integration is missing |
| 12:09 | <hallvors> | So..you're saying there is no authoritative definition of Focus to link to at the moment? |
| 12:11 | <hallvors> | But once there is one, I should hook things up |
| 12:12 | <annevk> | hallvors: HTML is the authoritative definition |
| 12:12 | <annevk> | hallvors: I'm just saying that I don't really know the specifics of focus since I haven't studied that in detail |
| 12:12 | <annevk> | hallvors: that's why I suggested you file some issues (also for DataTransfer) |
| 12:23 | <hallvors> | https://w3c.github.io/html/editing.html#focused and https://w3c.github.io/html/editing.html#focusable might define the concepts we should reference. |
| 12:25 | <annevk> | hallvors: you should definitely not reference the fork... |
| 12:25 | <hallvors> | s/w3c.github/specs.whatwg or something |
| 12:25 | <annevk> | hallvors: but e.g., https://html.spec.whatwg.org/multipage/interaction.html#focused seems reasonable |
| 12:26 | hallvors | doesn't like politics |
| 12:26 | hallvors | actually likes politics when it is about real issues |
| 12:26 | <annevk> | hallvors: just think of it as the wrong link then |
| 12:26 | <annevk> | hallvors: since it'll lead to the wrong thing being implemented |
| 12:27 | <annevk> | it's not really a political thing at that point |
| 13:01 | <zcorpan> | Is there a bug in github's UI? Twice now while navigating the UI, the green button says "Confirm squash and merge" but I have NOT clicked "Merge pull request" |
| 13:02 | <zcorpan> | e.g. reloading the page is enough |
| 13:06 | <annevk> | zcorpan: dunno, just got the same |
| 13:34 | <annevk> | Domenic: where should https://www.w3.org/Bugs/Public/show_bug.cgi?id=26182 go? |
| 13:35 | <Domenic> | annevk: https://github.com/whatwg/console/issues |
| 13:38 | <annevk> | Domenic: thanks, moved there |
| 13:43 | <zcorpan> | The commit message also has doubled linebreaks in the textarea... Such confidence |
| 16:55 | <MikeSmith> | https://developer.microsoft.com/en-us/microsoft-edge/platform/issues/ |
| 16:55 | <MikeSmith> | new it seems |
| 17:50 | <annulen> | GPHemsley: in https://mimesniff.spec.whatwg.org/#rules-for-identifying-an-unknown-mime-type 7.1.1 ends with "What about feeds?" question. I wonder, was there any discussion on this topic? |
| 17:50 | <annulen> | also, what about SVG? AFAIU, according to this section it should end up as text/xml |
| 18:55 | <Domenic> | This is amazing https://developer.microsoft.com/en-us/microsoft-edge/platform/catalog/ |
| 18:55 | <Domenic> | Scrapes current specs and compares against all browser IDLs |
| 18:56 | <Domenic> | Using open source data for everyone but Edge, and internal data for Edge. |
| 19:23 | <zcorpan> | nice! |
| 19:23 | <zcorpan> | DOM2 Style but not CSSOM |
| 19:29 | <zcorpan> | the visualization looks like a Venn Diagram but it looks like it only changes the size of the balloons, and the intersection is the same? |
| 19:49 | <zcorpan> | annevk: HTMLHyperlinkElementUtils doesn't provide a searchParams getter? is that intentional? |
| 20:30 | <Domenic> | annevk: custom elements DOM+ parts is ready for another look after your last round of excellent feedback. It's ready for upstreaming IMO, but you might find new bugs. |