03:27
<Hixie>
SamB: what do you want to do with the resources?
03:31
<SamB>
Well, logo.svg would look nice on the WHATWG article, obviously, though I guess it could be done as "fair use" on en.wp ...
03:36
<SamB>
(note that commons doesn't seem to require any trademark-related rituals)
03:41
<SamB>
of all the pointless ...
03:41
<SamB>
<link rel="shortcut icon" href="/favicon.ico" />
03:44
<Hixie>
pretty sure that would just be fair use regardless of copyright
03:48
<SamB>
but that's only actually allowed on the English wikipedia
04:20
<SamB>
hmm, you guys haven't been keeping the PNGs up to date ...
04:56
<zewt>
well, "fair use" isn't something that exists everywhere
04:57
<zewt>
as I (incompletely) understand things
05:02
<SamB>
zewt: yes, that would be why it's not allowed on the other wikipedias. even though they're all hosted in the US.
05:03
<zewt>
shouldn't be allowed on any of them
05:05
<SamB>
well, it's not FUN on any of them
06:30
<SamB>
its's too bad PNG only supports up to 256-entry palettes ...
07:41
<SamB>
hmm, rsvg does not grok logo-xhr.png ...
10:11
<MikeSmith>
foolip: could you review a MediaSource test?
10:57
<foolip>
MikeSmith: I could try
10:58
<MikeSmith>
foolip: cool, gimme a minute I'll get you the critic URL
10:59
<MikeSmith>
foolip: https://critic.hoppipolla.co.uk/r/911
10:59
<MikeSmith>
actual PR is https://github.com/w3c/web-platform-tests/pull/708
11:01
<foolip>
MikeSmith: oh look, you're the author
11:07
<MikeSmith>
heh
11:07
<MikeSmith>
foolip: yeah should I have disclosed that first?
11:21
<foolip>
MikeSmith: not really, I just assumed things :)
11:22
<MikeSmith>
:-)
11:28
<foolip>
MikeSmith: you should ask Ms2ger for review as well
11:29
<Ms2ger>
No you shouldn't ;)
11:29
Ms2ger
lunches
11:33
<foolip>
MikeSmith: you have some issues to look at now anyway :)
11:34
<MikeSmith>
foolip: cool -- thanks much
12:00
<Ms2ger>
MikeSmith, see html/dom/interfaces.html, fwiw
12:01
<MikeSmith>
Ms2ger: yeah I've looked at it before
12:02
<MikeSmith>
I will look at it more
12:53
<MikeSmith>
foolip: Thanks -- from your review comments I realize I can simplify the test quite a bit (since after all it really only needs to test the IDL support). So I'll make the change you suggested about putting all of the setup in an async test and running the IDL tests after that's done. (And push a change later for re-review but I think that next review won't cost much time.)
16:28
<SamB>
gah, I meant to say rsvg doesn't like logo-xhr.svg obviously
17:12
<dglazkov>
good morning, Whatwg!
20:40
<Ms2ger>
<doctype !html>
21:04
<SamB>
where do I report a bug in <http://www.w3.org/TR/SVGMobile12/paths.html#PathData>; ...
21:05
<heycam>
SamB, please report bugs to www-svg⊙wo but note that nobody really looks at /TR/SVGMobile2 -- check http://svgwg.org/svg2-draft/paths.html instead
21:05
<SamB>
heycam: ah
21:12
<SamB>
anyway, it seems to refer to both "instructions" and "commands" without making it clear what, if anything, is the difference between them
21:15
<arunranga>
Hi Ms2ger, are you around?
21:16
<Ms2ger>
Briefly
21:16
<heycam>
SamB, (without looking) no difference
21:16
<heycam>
I wonder: are there any specs that define !important UA style sheet rules?
21:16
<arunranga>
You recently closed https://bugzilla.mozilla.org/show_bug.cgi?id=978924 but even your test case shows inconsistencies in event firing across browsers. I've changed the spec., but I think the bug still stands.
21:17
<arunranga>
I think your test case should be added to it.
21:19
<Ms2ger>
arunranga, yeah, Chrome is wrong, it dispatches async
21:21
arunranga
hmmm… you're right that abort() is synchronous…
21:57
<Domenic_>
Hixie: http://esdiscuss.org/topic/es6-tasks-and-taskqueues#content-3
21:58
<Hixie>
microtasks only have one queue per event loop, btw
21:59
<Hixie>
as far as HTML goes, i have no desire to pretend it's distinct from ES... my goal was to hook in the ES spec into the HTML spec
21:59
<Hixie>
by making use of hooks provided by the ES spec
22:00
<Domenic_>
oh i thought there were several microtasks queues last i looked ... custom elements, then table sorting, then mutation observers, etc.
22:00
<Hixie>
they're all getting collapsed into one
22:00
<Domenic_>
i feel like that order is a bit strange given how underspecified ES is
22:00
<Domenic_>
ah cool
22:01
<Hixie>
i'm waiting for mutation observers to jump onte the train before doing table sorting
22:01
<Domenic_>
has anyone even announced intent to implement table sorting? :( :( :(
22:02
<Hixie>
no :-(
22:02
<Hixie>
tons of author demand, though
22:04
<Domenic_>
siiigh
22:48
<rafaelw>
Domenic_: ping.
22:49
<rafaelw>
(about es6 task vs microtask issue)
22:58
<SamB>
oh, I figured out why logo-xhr was so troublesome ;-)
23:15
<Domenic_>
rafaelw: pong
23:19
<rafaelw>
do you understand how modules work?
23:19
<rafaelw>
I just skimmed the spec, but I'm still pretty fuzzy on the actual mechanics.
23:20
<rafaelw>
I might have naively expected modules to need to enqueue Task work (as opposed to Microtask work)
23:20
<rafaelw>
but maybe they don't.
23:20
<rafaelw>
any idea?
23:29
<jsbell>
rafaelw: from my attempt to understand/model module loading and skimming the spec and pawing through https://github.com/jorendorff/js-loaders the behavior is described in terms of Promises, so it should only be microtasks, but I'm equally curious in an authoritative answer.
23:29
<Domenic_>
rafaelw: my understanding is they delegate everything to promises, yeah.
23:30
<Domenic_>
jorendorff was quite pleased when he realized he wouldn't have to do any of the event loop stuff himself :P
23:30
<rafaelw>
but presumably, Task work is taking place, right? IOW, when some bytes actually load off the network, something gets queue to handle the bytes being loaded and continue the loading pipeline?
23:30
<rafaelw>
gets queued
23:31
<jorendorff>
Domenic_: it was a miracle
23:31
<jorendorff>
Domenic_: and not because i'm lazy although i am
23:31
<jorendorff>
Domenic_: but because instead of specifying details of behavior, i could lean on the conventions baked into the Promise design
23:38
<Domenic_>
rafaelw: yes, if I am understanding correctly. When the bytes arrive you call EnqueueTask("PromiseTasks", ...stuff that causes the bytes to be used...)
23:39
<rafaelw>
Hmm. ok, so maybe the es6 can leave the outer event loop as an implicit concept.
23:40
<rafaelw>
And what is the "Script Evaluation Tasks" task queue used for?
23:41
<Domenic_>
I haven't seen that one...