04:35
<jsx>
In the xhr docs on MDN, it says that "Note: Any event listeners you wish to set must be set before calling send()", but I couldn't find anything related being said in the spec.
04:35
<jsx>
So I was wondering if it is more of a best practice than a rule.
06:21
<MikeSmith>
annevk: ⬆
06:23
<annevk>
jsx: iirc that is used for cross-origin fetches, and probably only for "upload".
06:44
<jsx>
annevk: thanks!
08:46
<yoav>
annevk: thoughts on https://github.com/w3c/preload/issues/36#issuecomment-185270277 ?
09:45
<zcorpan>
TabAtkins: ok, https://github.com/whatwg/wattsi/pull/21 should fix it
10:04
<MikeSmith>
zcorpan: on the train atm but will take a look at the PR in a couple hours
10:04
<zcorpan>
MikeSmith: ok thx
11:50
<MikeSmith>
zcorpan: IMHO it’s fine for that change to generate more automated IDs
11:50
<MikeSmith>
it would not be the first time that happened
11:51
<MikeSmith>
I don’t think we should do it cavilierly, but if there’s something else it buys us then we shouldn’t jump through hoops to avoid it
11:52
<MikeSmith>
that said, I kinda don’t like making changes just to make Shephard happy
11:52
<MikeSmith>
would rather Shephard changed to accommodate HTML
14:20
<iminUI>
Hello everyone. I recently joined a company as a Jr.UI developer. Excited to be a part of the community :)
14:22
<annevk>
hi iminUI, welcome
14:28
<iminUI>
thank you annevk
14:45
<zcorpan>
MikeSmith: how should Shepherd know that <h5 id="classes">The <dfn><code>class</code></dfn> attribute</h5> is a global attribute? This doesn't follow any pattern and there's basically nothing it can pick up on here, afaict
14:46
<zcorpan>
MikeSmith: i guess it could analyse the "source" file instead and implement the same dfn->ID mapping as wattsi does, but that also seems a bit insane
14:52
<zcorpan>
idea for httparchive fans: compare total image size for pages that use picturefill vs. pages that don't. (assuming here that using picturefill is a rough approximation for "using <picture> or srcset")
15:55
<rbyers>
birtles: Hey, in Sydney you said you thought we should still be trying to ship the Event.timestamp HighResTimeStamp change, still feel that way? Care to comment on https://github.com/whatwg/dom/issues/23 ?
17:07
<Ms2ger>
GPHemsley, hey, you got plans to move / objections to moving mimesniff to bikeshed?
17:07
<Ms2ger>
(After paul's patches land)
18:53
<TabAtkins>
MikeSmith: Shepherd is already bending over backwards trying to guess as accurately as possible what all of HTML's definitions are. ^_^ Some things are just impossible, like this one - there is absolutely no way a machine can tell that header is a dfn for the class attribute without just adding an explicit thing saying "this is the anchor for the class
18:53
<TabAtkins>
attribute".
20:48
<zcorpan>
should we have a label for authoring conformance/validators?
20:50
<Domenic>
seems like a good idea, yeah
20:58
<zcorpan>
"topic: validators"?
21:44
<Domenic>
I'd say more of a cross cutting "authoring conformance" tag. Topics IMO should be things that show up in the TOC.
23:28
<MikeSmith>
I much prefer “conformance checkers” rather than “validators”
23:28
<MikeSmith>
and “document conformance” rather than “authoring conformance”
23:30
<MikeSmith>
because a document needs to be evaluated in isolation from whoever authored it
23:31
<MikeSmith>
TabAtkins: yeah zcorpan already clarified that for me a bit, about the problem case
23:32
<MikeSmith>
but IMHO the right way to solve it would be to just put the IDs in the source rather than having wattsi generate them
23:33
<MikeSmith>
or rather than letting wattsi munge them
23:35
<MikeSmith>
the latest comment I saw from Domenic on the wattsi issue seems to make it clear that the problem we have is with wattsi doing that ends up with not the right markup in the output even if we have the right IDs in the source
23:36
<MikeSmith>
so I would prefer that we fix that rather than trying to further tweak wattsi’s behavior for generating IDs