00:46
<mrbkap>
dglazkov: Are you still there?
00:46
<dglazkov>
mrbkap: yup
00:48
<mrbkap>
dglazkov: Are lifetime callbacks supposed to be called in order of when they are generated globally or in order for their microtask?
00:50
<mrbkap>
dglazkov: I might be lost in the spec, but I think the way it's specified right now, the spec might end up processing the same lifetime callbacks multiple times.
00:50
<dglazkov>
mrbkap: the element/callback queues is what provides the order.
00:50
mrbkap
doesn't have a concrete example yet.
00:53
<mrbkap>
dglazkov: I think I'm having a hard time reasoning about this because the spec puts the lifetime callback queues on the elements themselves.
00:53
<mrbkap>
dglazkov: Which means that when a lifetime callback recursively causes another lifetime callback, we push that element onto the new queue.
00:54
<zewt>
perplexed at chrome messing up with simple things, like how ^T opens at tab way at the end of the tabs, instead of after the focused tab
00:54
<dglazkov>
mrbkap: there's only one queue per element, so that shouldn't happen
00:54
<zewt>
on the web, apparently no problems are really solved problems
00:54
<mrbkap>
oops, I missed that we remove each processed callback before calling it.
00:55
<mrbkap>
okay, cool.
00:55
<dglazkov>
yay!
00:56
<darobin>
serious side-effects of jet lag: seeing dglazkov in the morning
00:56
<dglazkov>
cannot be unseen
00:56
<mrbkap>
With enough alcohol...
00:57
<darobin>
with enough alcohol he starts being a voice in your head
01:07
<TabAtkins>
Ms2ger: The errata is public, but I forget where. It's hidden somewhere stupid.
01:22
<dglazkov>
darobin: that's the final phase
01:23
darobin
shudders at the thought of what happens after that...
01:23
<dglazkov>
darobin: btw, did you see that hayato converted shadow DOM spec to ReSpec?
01:23
<dglazkov>
http://w3c.github.io/webcomponents/spec/shadow/
01:25
<darobin>
oooh
01:25
<nimbu>
omg the SPEC OF SHADOWS
01:26
<darobin>
286 warnings, nice :)
01:29
<darobin>
dglazkov: this is sweet; if hayato has any questions I'm happy to help any time
01:30
<darobin>
oh, and I hadn't noticed that webcomponents had moved to GH, that's much better than dvcs.w3
01:41
<MikeSmith>
I hear http://memecrunch.com/generator/custom/ is working as expected again now
01:42
<nimbu>
whats the best new memes on W3C since TPAC
01:42
<nimbu>
or wait is tpac still going on
01:43
<darobin>
nimbu: tpac is still on
01:43
<nimbu>
darobin: are you all wearing the beloved mandrin tpac shirts
01:43
<nimbu>
making you look like party members
01:43
<darobin>
nimbu: not I at this moment, but there's a lot of that going on yes
01:43
<nimbu>
darobin: you all gotta take group photo wearing that
01:44
<TabAtkins>
nimbu: TPAC is, in fact, happening at this very moment.
01:44
<nimbu>
sylvain needs to get a hat with that long hair
01:44
TabAtkins
has been attending from California this week.
01:44
<darobin>
nimbu: yeah, that's a good idea actually
01:44
<nimbu>
TabAtkins: ahaha that sounds like a nightmare
01:44
<nimbu>
to attend from california
01:44
<TabAtkins>
It's kinda bad, but whatever. Meetings go from 5pm to 2am.
01:44
<nimbu>
:||||||||||||||||||||||||||||||||||||||||||||||||||||
01:44
<nimbu>
cray
01:45
<nimbu>
darobin: MAKE IT HAPPEN ROBINNNNNNNNNNNN
01:45
<nimbu>
YOU DA MAN
01:45
<darobin>
5pm to 2am isn't so bad
01:45
<darobin>
it could be the other way around
01:48
<darobin>
nimbu: I'm not sure if I can get a bunch of TPAC people doing that, on the fourth evening people are completely unmanageable
01:48
<darobin>
(as opposed to the first evening, where everyone is piled up on the same table drinking)
01:48
<darobin>
but there's a team meeting on Sunday, so you might expect at least that pic with the whole w3c :)
01:48
<nimbu>
:)))
01:48
<nimbu>
YES PLZ
01:49
<nimbu>
i am sure someone can make a meme picture out of it
01:49
<nimbu>
okay GTG BAI TPACS
01:49
<TabAtkins>
darobin: You can always get a picture at the werewolf game.
01:50
<darobin>
TabAtkins: yeah, but that's only ~25 peeps
04:00
<zewt>
oops, did view image on a 1920x1080 pixel canvas in firefox
04:00
<zewt>
time to wait for the braindamaged thing to put a ~10mb data url in the address bar
04:01
<zewt>
one case where persisting a blob url would be a big win
04:38
<zcorpan>
should we make EventSource() Worker() SharedWorker() use utf-8 as the url character encoding?
09:16
<zcorpan_>
jgraham_: why does http://software.hixie.ch/utilities/js/live-dom-viewer/saved/2636 time out the harness?
09:20
<zcorpan_>
looks like done() is broken? http://software.hixie.ch/utilities/js/live-dom-viewer/saved/2637
09:20
<zcorpan_>
jgraham_: ^
14:42
<zcorpan>
can someone merge https://github.com/w3c/web-platform-tests/pull/243 kthxbye
14:44
<Ms2ger>
"We can�t automatically merge this pull request"
14:44
<Ms2ger>
Oh, and that someone would need to fix up the whitespace
14:46
<jgraham_>
I am on it
14:51
Ms2ger
wonders why zcorpan asked
14:52
<Ms2ger>
Okay, that someone didn't fix the whitespace?
14:52
<jgraham_>
Ms2ger: I don't understand the question, but I fixed the merge conflict and pushed
14:53
<zewt>
if(undefined == toStart) yoda conditionals write not
14:53
<Ms2ger>
And Yoda definitely wouldn't use ==!
14:54
<zewt>
someone i know uses yoda conditionals ... for inequalities D:
14:55
<zewt>
it both makes things impossible to read, and even misses the original *point* (as misguided as it is) of yoda conditionals
14:56
<Ms2ger>
if (undefined !== foo)?
14:57
<zewt>
if(0 < foo && 10 > foo)
14:58
<Ms2ger>
Still not as bad as lisp
14:58
<Ms2ger>
(if (< 0 foo)...
15:28
<FireFly>
(if (< 0 foo 10) ...
15:39
<Ms2ger>
TabAtkins, yeah, that was what I was thinking too... Let me know if you ever find it (re css2.1+)
15:41
<jgraham_>
?iffoo < 0 if foo [...] then;
15:42
<jgraham_>
I think
15:42
<Ms2ger>
jgraham_, what's that?
15:42
<jgraham_>
Forth, I think
15:43
<jgraham_>
Well it was intended to be, but I have never written any forth in my life
15:43
<zewt>
wow what the
15:43
<Ms2ger>
Reverse Polish, eh
15:43
<zewt>
now some w3c tracker page keeps randomly trying to close
15:44
<zewt>
i'm off doing something else and a chrome window steals focus to go ARE YOU SURE YOU WANT TO LEAVE
15:44
<jgraham_>
Yeah, I think you put < and 0 on the stack and then if pops the last two items on the stack, or something
15:44
<zewt>
i don't even know which one, since the focused tab is ... gmail
15:44
<jgraham_>
Oh, probably don't have "foo"
15:47
<jgraham_>
Maybe ?foo 0 < [...] then ;
15:47
<jgraham_>
This is probably not the right forum to learn stack-based programming in real time without actually trying to think
15:47
Ms2ger
wonders how jgraham_ ended up with Forth
15:48
<jgraham_>
I was thinking of languages that would have weirder if syntax than lisp
15:48
<Ms2ger>
Ah
16:11
<MikeSmith>
Ms2ger: I really don't remember initiating a PR with a th.js file in it
16:12
<Ms2ger>
MikeSmith, no, I meant a PR of mine in the testharness.js repo
16:12
<MikeSmith>
oh
16:12
<Ms2ger>
But you were talking about w3c-test:mirror on wpt, I think
16:12
<MikeSmith>
ah that
16:12
<MikeSmith>
yeah
16:13
<Ms2ger>
Anyway, class over
16:13
<MikeSmith>
sorry for that noise
16:13
Ms2ger
poofs
16:13
<Ms2ger>
Np
16:23
<espadrine>
where are w3c css tests going? Should they be in <https://github.com/w3c/web-platform-tests>;? What's the status?
16:26
<MikeSmith>
espadrine: in a separate repo
16:26
<MikeSmith>
a mercurial repo
16:26
<MikeSmith>
at dvcs.w3.org
16:26
<MikeSmith>
and then they get mirrored at github
16:26
<espadrine>
MikeSmith: oh, found it, <https://hg.csswg.org/test/>;
16:27
<MikeSmith>
OK
16:27
<espadrine>
thanks
17:11
<SimonSapin>
espadrine: I believe the plan it to move CSS tests into web-platform-tests, but there is also a bunch of infrastructure to port https://test.csswg.org/shepherd/
17:13
<MikeSmith>
SimonSapin: I think it's safe to say there's a low chance of the Shepherd stuff every getting used by any other groups except CSS
17:13
<espadrine>
SimonSapin: ah ok
17:14
<MikeSmith>
I don't know what the current state of discussion around porting it over to w-p-t but if it is brought over, it'll be only for use by the CSS WG
17:16
<MikeSmith>
I think (hope) that the long-term plan is to come up with a common system that meets whatever the same basic use case is that Shepherd was intended for, but that's instead based on requirements that we all actually agree with
17:17
<MikeSmith>
instead of what Shepherd is based on, which if it's like the rest of the CSS WG infrastructure, is based on idiosyncratic requirements that the CSS WG is the only group that has
17:17
<MikeSmith>
or claims to have
17:17
<MikeSmith>
anyway
17:27
<dglazkov>
good morning, Whatwg!
17:28
<SimonSapin>
MikeSmith: I don’t know more than that, I only heard about it yesterday
17:28
<SimonSapin>
but yes, this would be a good conversation to have
17:28
<MikeSmith>
SimonSapin: yeah
17:28
<SimonSapin>
probably with plinss
17:29
<MikeSmith>
jgraham_ and tobie and rebecca hauck have already been discussing it with peter linss
17:29
<MikeSmith>
SimonSapin: yeah
17:40
<Ms2ger>
Fwiw, my approach to CSS tests right now is "wait"
17:44
<MikeSmith>
that seems to be everybody's approach right now
17:44
<MikeSmith>
I think Peter may be waiting for it to never happen
17:44
<MikeSmith>
waiting it out
17:53
<hober>
wu wei
17:56
<MikeSmith>
hober: another master for us to learn from
17:57
<Ms2ger>
I guess if it doesn't work out, I'll just start putting tests into wpt
18:08
<hsivonen>
argh. I read some www-tag email and now I'm agitated about proposals to sniff bomless UTF-32
18:33
<SimonSapin>
hsivonen: I want to kill most of http://www.w3.org/TR/CSS21/syndata.html#charset , but I really don’t want to argue about it in a meeting :/
18:34
<Ms2ger>
Watch out, you might end up in a meme that way
18:36
<MikeSmith>
that might be an uncomfortable place to be tonight
22:31
<Hixie_>
huh
22:32
<Hixie_>
navigating to javascript:foo essentially does the same as document.open();document.write(eval('foo'));document.close()
22:33
<Hixie_>
hm, no, nevermind
22:33
<Hixie_>
i misinterpreted the result of a test
23:34
<Hixie_>
annevk: yt?
23:42
<Hixie_>
section 3.2 of http://tools.ietf.org/id/draft-hoehrmann-javascript-scheme-00.txt is awesome
23:42
<Hixie_>
it sounds fancy, but the four steps boil down to:
23:42
<Hixie_>
1. get the data
23:42
<Hixie_>
2. figure out what to do with the data
23:42
<Hixie_>
3. do it, and remember the result
23:42
<Hixie_>
4. process the result
23:43
<Hixie_>
(with no more detail than that, except step 1 points to an algorithm to say how to get the data)
23:43
<Hixie_>
section 3.1 is the only section of that spec that's not trivial
23:44
<Hixie_>
let's see if it's right...
23:45
<Hixie_>
uh oh, i might need to hand-parse the URL field
23:45
<Hixie_>
that ought to be fun