06:10
<annevk>
GPHemsley: graag gedaan
07:47
<annevk>
So my theory with all the weird IDNA problems we're seeing is that implementers have some checks reversed
07:47
<annevk>
They only do full ToASCII if there are no ASCII code points
07:48
<annevk>
Otherwise they don't care and just pass it along without much validation
07:48
<annevk>
Whereas UTS 46 does apply a bunch of processing even to plain ASCII input
07:48
<annevk>
I guess I should write some more tests and then raise this somehow
09:26
<annevk>
(If whatwg.org goes down, please ping me.)
14:49
<kiwi_12705>
DOM says "Event listeners key off the event’s `type` attribute value"
14:49
<kiwi_12705>
What does it mean?
15:40
<annevk>
Hmm, maybe we should indicate on the IRC page that it can take a while before you get a reply
16:01
<annevk>
(done)
16:28
<annevk>
JakeA: can you figure out why https://bugs.chromium.org/p/chromium/issues/detail?id=365070 never went anywhere?
16:28
<annevk>
JakeA: is it something Chrome just doesn't want to do, or did the bug never got the attention from the right people?
16:29
<annevk>
(I emailed someone at Mozilla to get an equivalent answer for https://bugzilla.mozilla.org/show_bug.cgi?id=998590.)
16:30
<JakeA>
annevk: I haven't figured that it yet. Trying to work out if it breaks existing sites.
16:30
<JakeA>
that out*
16:31
<annevk>
JakeA: not all existing sites use <h1-6> correctly either, so I doubt the outline is always useful
16:32
<JakeA>
annevk: yeah, it comes down to "does it make things significantly worse vs better"
16:32
<JakeA>
Not sure how to test that other than manually
16:32
<annevk>
JakeA: it's still interesting though why it was never picked up to begin with
16:33
<annevk>
JakeA: since at some point in the past <section> wasn't a thing and wouldn't really be able to impact sites significantly
16:33
<annevk>
JakeA: maybe there's some hidden opposition to the feature?
16:33
<JakeA>
annevk: it might slow things down, but we could have restricted the cost to AT users
16:33
<annevk>
I guess keeping it all work dynamically adds some cost
16:34
<JakeA>
annevk: I'm guess it was just low priority because it's a11y + new
16:34
<annevk>
But it can't be that much
16:34
<JakeA>
Agreed
17:19
<boogyman>
JakeA: where should I report a media playback issue for Chrome Canary?
17:40
<JakeA>
boogyman: crbug.com
17:44
<boogyman>
oh, duh. cheers