| 05:25 | <Manishearth> | anyone around? |
| 05:32 | <Manishearth> | Hixie_: in https://html.spec.whatwg.org/multipage/forms.html#constructing-form-data-set , are empty names ok? |
| 05:32 | <Manishearth> | it seems like most browsers ignore elements with empty names, but the spec seems to allow <input type=text> and <button type=submit> to have empty names |
| 05:34 | <Manishearth> | I don't see where that gets filtered out |
| 09:14 | <nox> | Manishearth: "The field element is not an input element whose type attribute is in the Image Button state, and either the field element does not have a name attribute specified, or its name attribute's value is the empty string." |
| 09:14 | <nox> | Manishearth: Step 3.1., bullet 6. |
| 09:16 | <Manishearth> | nox: ... I'm blind |
| 09:16 | <nox> | Manishearth: No, you are reading HTML. |
| 09:17 | <Manishearth> | :) |
| 11:22 | <Ms2ger> | Someone remind me: can two same-origin tabs communicate synchronously? |
| 11:25 | <ondras> | as long as they have references to each other |
| 11:26 | <ondras> | as in, var w = window.open("...sameorigin", "_blank") |
| 11:26 | <ondras> | w.doStuff() |
| 11:46 | <annevk> | Oh cool, Chrome and Safari differ in what gets to be the referrer global |
| 11:46 | <Domenic> | not even a little surprised |
| 11:54 | <annevk> | Chrome and Safari differing is somewhat unusual, but maybe not when it comes to the network stack. Although it still seems weird they'd pass different parameters down |
| 11:54 | <annevk> | Firefox and Safari are on the same line and for some reason Edge always has document.referrer as the empty string so is hard to debug... |
| 12:02 | <annevk> | Hmm |
| 12:02 | <annevk> | Domenic: a navigated <iframe> is not going to really affect things for https://github.com/whatwg/html/issues/1130#issuecomment-220671949 is it? |
| 12:03 | <annevk> | Domenic: because whatever pointer I have to the Window is really a pointer to the WindowProxy which remains the same |
| 12:03 | <Domenic> | annevk: uhhh hard for me to really grapple with multi-global questions in the middle of TC39 while jetlagged ;P |
| 12:04 | <annevk> | Domenic: hehe, I'll pester bz when he wakes up then |
| 12:28 | <Domenic> | annevk: how do you make wattsi spit out the dev version? |
| 12:28 | <Ms2ger> | ondras, okay, insert "independently opened by the user" :) |
| 12:29 | <annevk> | Domenic: I thought that happened automatically |
| 12:29 | <Domenic> | oh maybe... i'll go check the output directory |
| 12:30 | <Domenic> | hmm i don't see it |
| 12:30 | <Domenic> | at least when using build.sh |
| 12:32 | <Domenic> | i bet it's in the temp directory |
| 12:32 | <annevk> | Domenic: yeah, we might not copy it at the moment |
| 12:33 | <Domenic> | yeah found it |
| 12:55 | <ondras> | Ms2ger: okay, I am not aware of any way then :) |
| 15:16 | <annevk> | Domenic: is anyone from Apple attending the meeting? |
| 15:16 | <Domenic> | annevk: yep |
| 15:16 | <annevk> | Domenic: it might be interesting to ask them about their global setup and incumbent/current/relevant and such |
| 15:16 | <Domenic> | hmmm |
| 15:17 | <annevk> | Domenic: basically in my tests it seems like sometimes Apple uses entry and sometimes incumbent, for something where there's really only one answer possible |
| 15:17 | <Domenic> | yeah worth checking, although js engine devs and web platform don't always cross over |
| 15:17 | <annevk> | Domenic: so it seems like they have at least one concept less |
| 15:17 | <annevk> | Domenic: true |
| 15:17 | <Domenic> | annevk: you realize we want to get rid of both and use "current" mostly? :) |
| 15:17 | <annevk> | Domenic: I'm looking at navigations (through location / window.open) |
| 15:18 | <annevk> | Domenic: so while there's some wiggle room, I doubt there's that much |
| 15:18 | <Domenic> | mmm yeah |
| 15:26 | <annevk> | It was kinda nice once I understood the specification you just wrote, but it turns out not everyone implements it (or has super weird logic elsewhere) |
| 15:26 | <annevk> | 😟 |
| 17:10 | <TabAtkins> | gsnedders: A streaming parser won't pre-scan the byte stream. (Or I guess will scan it with a length of 0, if you want to push this into trivialities.) |
| 17:26 | <jyasskin> | annevk: In case it helps, I believe Blink's current/entry/incumbent logic is https://code.google.com/p/chromium/codesearch/#chromium/src/third_party/WebKit/Source/bindings/core/v8/V8Binding.cpp&l=672-704. |
| 17:26 | <jyasskin> | Only incumbent is used significantly outside of location. |
| 17:29 | <annevk> | jyasskin: thanks, it might help, though for what I'm looking at it seems like Blink is an outlier |
| 19:33 | <gsnedders> | TabAtkins: duh. ofc, the streaming case. |
| 20:48 | <gsnedders> | Probably missing something obvious, but: why can't CSS `background` apply to SVG elements? |
| 20:50 | <tantek> | gsnedders: perhaps it's just not defined how it applies? |
| 20:50 | <tantek> | and SVG already has 'fill' |
| 20:56 | <gsnedders> | tantek: tl;dr: I want to apply a background a dynamically generated text element. fill there alters the colour of the text, not its background. |
| 20:57 | <tantek> | gsnedders: I think you have to apply the fill to the parent of the text |
| 21:00 | <gsnedders> | tantek: right, which means dynamically hacking around with the tree after the library generated it, which is extra complexity I was hoping to avoid |