00:04
<Domenic>
annevk: going to write tests for https://github.com/whatwg/html/pull/1986 ?
01:18
<MikeSmith>
smaug: it looks like https://www.w3.org/TR/2003/WD-DOM-Level-3-Events-20030221/DOM3-Events.html#changes-DOMLevel2to3Changes-h3 is when it was added
01:18
<MikeSmith>
smaug: 2003
01:19
<MikeSmith>
smaug: > The Event interface has a new attribute namespaceURI, and a four new methods: isDefaultPrevented, isCustom, stopImmediatePropagation, isPropagationStopped, initEventNS.
01:19
<smaug>
hmm
01:19
<smaug>
MikeSmith: what was my question? :)
01:19
<MikeSmith>
looking to see if there is more detailed changelog somewhere
01:19
<MikeSmith>
haha
01:20
<MikeSmith>
oofs
01:20
<MikeSmith>
was mounir I guess actually
01:20
<MikeSmith>
not you
01:21
<smaug>
ah, I see there
01:56
<mounir>
MikeSmith: thanks :)
01:56
<mounir>
MikeSmith: any idea why it was added? I wonder what are the use cases behind it
01:58
<MikeSmith>
mounir: I pinged plh to ask him if he remembers (or even if he doesn’t remember at least he can look back at his old editor drafts or whatever and piece it back together)
01:58
<MikeSmith>
mounir: yeah I have no idea personally
01:58
<MikeSmith>
but plh has a pretty good memory
01:59
<MikeSmith>
and he was editing that spec at the time
02:00
<MikeSmith>
I already checked the old mail archives, including the Member-only ones, but could find no clues there
02:09
<mounir>
MikeSmith: thanks :)
02:09
<mounir>
MikeSmith: hopefully with GitHub repos and proper commit mesages, there will be no need for archeologic searches in the future :)
02:13
<MikeSmith>
mounir: yes
04:09
<rbyers>
tobie: Sorry for the delay. Yeah that was just a test team mistake - removed it. bashi@ is the bindings lead.
08:02
<tobie>
rbyers: ok cool. Thanks. :)
09:37
<annevk>
tobie: it seems I missed something yesterday, "record" is not exported, only "record type" is
09:37
<annevk>
tobie: that means that I can't link "is a record" yet and still can't land that Fetch patch :/
09:38
<tobie>
annevk: wait, what?
09:39
<annevk>
tobie: we landed a change to export "mappings" yesterday
09:39
<annevk>
tobie: but I also need "record" itself exported
09:45
<tobie>
annevk: I think we should write up what IDL should export by default.
09:45
<tobie>
annevk: would avoid wasting time like this.
09:45
<annevk>
tobie: the not exporting by default is mostly what's wasting time I think
09:46
<annevk>
tobie: esp since stuff like interface members, which prolly should not really be exported, are exported by default
09:46
<annevk>
tobie: anyway, I'm going to fix my tiny problem for now and let you worry about the big picture for IDL
10:29
<annevk>
Heh, https://twitter.com/m1sp/status/797177386408083456 got popular
10:31
<annevk>
TabAtkins: re https://twitter.com/tabatkins/status/797194521356300288 pretty sure Hixie/dhyatt came up with the name "shadow"
10:32
<annevk>
e.g., https://www.w3.org/TR/2006/WD-xbl-20060619/
10:32
<nox>
The only name I came up with is LegacyUnenumerableNamedProperties. FeelsBad.
12:44
<zcorpan_>
annevk: https://medium.com/@shahata/why-i-wont-be-using-fetch-api-in-my-apps-6900e6c6fe78 fyi
13:47
<annevk>
zcorpan: I read that, wasn't sure what to do with it
14:30
<annevk>
Domenic: landed a test for reset()
14:31
<annevk>
Domenic: can't really test the other thing as stated in the PR
14:36
<MikeSmith>
mounir: so about your question of why stopImmediatePropagation was added, plh helped me look back through the changelogs and discussion from the time when it when it was added, and the closest we got was https://lists.w3.org/Archives/Member/w3c-dom-ig/2003Feb/0041.html
14:37
<MikeSmith>
which is a message from Johnny Stenback
14:37
<Ms2ger>
I'm pretty sure you're not allowed to disclose that
14:37
<MikeSmith>
saying, “Need .stopAllPropagation() so that an app can completely stop anevent from firing anymore, period--not just for the current group. Itseems like this is something apps will need to use but I'm havingtrouble remembering the use cases for stopPropagation()”
14:38
<MikeSmith>
Ms2ger: oh
14:38
<MikeSmith>
yeah I guess you’re right
14:39
<jgraham>
I imagine jst will be horrified that you disclosed his useful technical contribution in a silly venue.
14:39
<MikeSmith>
yeah I couldn'
14:40
<MikeSmith>
yeah I couldn’t tell if Ms2ger was being facetious or not
14:41
<MikeSmith>
anyway we really need to just declassify all those member-only archives
14:41
<Ms2ger>
Oh come on, it's me you're talking about
14:41
<MikeSmith>
haha
14:41
<MikeSmith>
yeah
14:41
<MikeSmith>
I’m not trusting my own instincts much any more the last week or so
14:43
<annevk>
MikeSmith: oooh, I wish W3C would have a policy around declassifying archives
14:43
<MikeSmith>
I have talked to plh about it before
14:44
<MikeSmith>
but given all the other problems that need to get solved it never bubbles up to being a high enough priority
14:44
<MikeSmith>
not causing enough pain
14:44
<MikeSmith>
relative to e.g. what to do with TR
14:45
<MikeSmith>
but anyway it’s not for lack of realizing it’s a problem
14:46
<annevk>
MikeSmith: that email you pointed to and its replies seem to conclude to not add it
14:46
<MikeSmith>
yeah that is part of what is weird here
14:47
<MikeSmith>
there is a gap there
14:47
<MikeSmith>
in the record of the discussion in the when the change made its way into the spec
14:48
<MikeSmith>
it seems like there might have been some off-list and off-telcon discussion about it
14:48
<MikeSmith>
otherwise it just seems to have magically appeared
14:48
<annevk>
I think in practice events have been a little over engineered
14:49
<annevk>
But they work fine
14:50
<MikeSmith>
well if you read through the discussions from that time (which I was just doing today) they could have been even a lot more overengineered if some of what was being proposed had been added to the spec
14:50
<jgraham>
They work fine? That doesn't sound like the web I know.
14:50
jgraham
doesn't actually any any particular problems with events :)
15:51
<wanderview>
JakeA: is there a chrome issue for this? what are your plans for implementing? https://github.com/w3c/ServiceWorker/issues/787
15:51
<wanderview>
we're talking about implementing soonish
16:45
<zcorpan>
TabAtkins: how should global attributes be exported in html spec to be referenceable in bikeshed as <a element-attr for=???>accesskey</a> (or markup shorthand for that) ?
17:27
<gsnedders>
UTF-16-without-a-BOM works if user override is used and set to the appropriate encoding, is specificed at the transport layer, or is autodetected using frequency analysis or "other algorithms", right?
18:57
<TabAtkins>
annevk: I came up with the name "Light", tho.
19:05
<JakeA>
wanderview: will find out. Would be nice if we landed it at the same time of course
19:08
<wanderview>
JakeA: yea, thats what I was thinking... I think we have an extra 6 weeks from nightly to release compared from canary to stable, though
19:32
<TabAtkins>
zcorpan: That is a great question. I think I want to just mint a name for them? Like for=html-global or something.
19:33
<TabAtkins>
Something unlikely to ever be an actual HTML tagname, and which can be generalized to SVG/etc.
21:59
<Domenic>
zcorpan: TabAtkins: maybe *?
21:59
<TabAtkins>
Hmm, perhaps. Use html*/foo ?
22:00
<TabAtkins>
(On the assumption that SVG and HTML will have different global attributes allowed.)
22:00
<Domenic>
seems reasonable
22:00
<TabAtkins>
I don't think that'll parse right now, gimme a sec.
22:00
<Domenic>
class, id, and slot are superglobal, others are language-specific
22:01
<TabAtkins>
Oh no, it's fine, * is already recognized there for some reason. (Probably just cargo-culted from the property/etc regexes.)
22:01
<zcorpan>
ok
22:02
<TabAtkins>
So yeah, <{html*/accesskey}>.
22:02
<zcorpan>
now just need to export all attributes properly, to bikeshed html-differences
22:12
<zcorpan>
TabAtkins: https://github.com/tabatkins/bikeshed/pull/877 - i forgot to run tests clearly ^_^
23:16
<TabAtkins>
zcorpan: Nah, the tests aren't your fault, they're from a commit a bit ago. Just fixed them up; they just needed a rebase.
23:18
<zcorpan>
TabAtkins: ok thx