00:20
<Hixie>
jlebar: yeah, i could see an argument along those lines. Is there mail about it?
00:22
<jlebar>
Hixie: Yes, but it's hidden. :) Thread titled "AJAX History Concerns". Mail from me (justin.lebar⊙gc) on Nov 13.
00:23
<Hixie>
in that case i should get to it in due course
00:23
<Hixie>
is it urgent?
00:24
<Hixie>
i can move it up the list if it's urgent, though i'm swamped with mail right now so it'll still be a while
00:25
<jlebar>
Hixie: I think we're going to land pushstate soon, and although I've been saying that for a few months now, I finally have a few reviews done on it, so I think it might actually happen in the near future. It would be nice not to change it after we land it.
00:25
<Hixie>
ah, ok
00:26
<Hixie>
let me see, hold on
00:26
<jlebar>
I can go ahead and just take out the title parameter. We certainly don't have to have the replacement specified when we land pushstate.
00:27
<jlebar>
* by "the replacement", I mean the functionality for changing the history entry title by other means than push/replaceState.
00:31
<Hixie>
i need to start writing down my stack
00:31
Hixie
pops back down to jlebar's request
00:54
<Hixie>
jlebar: replied to your e-mail
00:56
<jlebar>
Hixie: Thanks.
01:01
<miketaylr>
brb
01:37
<jlebar>
Hixie: I just replied, but I'm going to get dinner now.
02:12
<Hixie>
http://wiki.whatwg.org/wiki/FAQ#What_are_the_various_versions_of_the_spec.3F
02:12
<Hixie>
!
02:30
<TabAtkins>
Hixie: Are you surprised that someone put it together?
02:32
<Hixie>
no, i just did
02:32
<Hixie>
i'm just surprised as to how long it turned out
02:35
<TabAtkins>
It is pretty damned long, I must admit.
02:35
<TabAtkins>
Clearly there are many representations of that resource. ^_^
02:36
<Hixie>
or there are many resources generated from the same source document :-P
02:37
<Hixie>
and it doesn't even include the out-of-date versions like the /TR/ page
03:24
<jlebar>
Hixie: The < in the example you just added with updating the title each second doesn't come through right.
04:35
<Hixie>
jlebar: fixed, thanks
08:26
<hsivonen>
gsnedders: what's the situation with the html5lib test suite and the state of the spec? are the tests up-to-date?
08:32
<hsivonen>
http://html5.org/tools/web-apps-tracker times out for me
08:33
<hsivonen>
is Dreamhost dreaming againg?
08:34
<hsivonen>
awesome. dreamhoststatus.com doesn't load in a reasonable time, either.
08:34
<hsivonen>
http://twitter.com/dhstatus/status/6002999309
09:07
<jgraham>
hsivonen: AFAIK gsnedders went and changed html5lib to match current spec so the tests should be up to date
09:08
<jgraham>
No promises and certainly no suggestion that all the intersting changed cases are covered
09:09
<hsivonen>
jgraham: ok. thanks
09:43
<gsnedders>
hsivonen: It's also quite likely that I missed some bits of the spec that had changed
09:47
<gsnedders>
Is it just me or is hixie.ch down?
09:47
<gsnedders>
Oh, DH network failure. Great.
09:48
<hsivonen>
gsnedders: ok. thanks
10:34
<Hixie>
dreamhost is back up for people who were complaining
10:35
<hsivonen>
great
10:35
<hsivonen>
doesn't look like it
10:35
<hsivonen>
html5.org and whatwg.org don't respond
10:36
<Hixie>
the network is back up
10:36
<Philip`>
What about for people who weren't complaining?
10:36
<Hixie>
the machines seem to be overloaded
10:36
<Hixie>
but they respond to ping
10:36
<Hixie>
and can be sshed into
10:36
<Hixie>
Philip`: i wasn't telling those people :-)
10:37
<Hixie>
hm, ssh broke
10:37
<Hixie>
still responding to pings though
10:45
<Hixie>
http seems to be back
10:49
<Philip`>
Hixie: In case you don't read it in IRC logs: SVN is inaccessible, and http://svn.whatwg.org/ gives a "Forbidden" error
10:49
<Hixie>
yeah, already reported it to them
10:49
<Hixie>
no idea why
10:49
<Hixie>
i created another repo and that one works fine
10:53
jgraham
wonders if dreamhost were imagining the kind of dream where you are being chased by monsters inexplicably wearing your pyjamas when they chose their name
10:54
<Lachy>
jgraham, they would have called themselves Nightmarehost if that was the case.
14:14
<hsivonen>
has <body> in 'after head' always set frameset-ok to 'not ok'?
14:16
<annevk2>
Hixie, you should look into fixing http://svn.whatwg.org/
14:16
<annevk2>
Hixie, if you're back and all
14:16
<annevk2>
Hixie, hmm, guess you're asleep now
14:20
<Philip`>
annevk2: He said he'd contacted Dreamhost about it already
14:21
<annevk2>
coolio
15:40
<Lachy>
I need to decide whether or not to incorporate any of these tests into the selectors api test suite, which is now mostly complete http://www.hixie.ch/tests/adhoc/dom/selectors/001.html
15:40
<Lachy>
the only tests that are failing are in WebKit, which has a strange NodeList implementation
15:41
<Lachy>
nodelist.elementid returns an element in the list with that ID, if it exists. (see tests 011 and 082)
15:42
<Lachy>
I'm not sure why it does that, but the NodeList behaviour doesn't really seem to be in scope of selectors api
15:42
<Lachy>
(beyond the list being static, rather than live)
15:48
<Philip`>
It seems "in scope" in the sense that it is a bug which could be encountered by an author who is using the Selectors API
15:48
<Philip`>
and so it's directly beneficial to the Selectors API if the bug is identified and fixed
19:00
<hsivonen>
Is there a way to track the Google Desktop integration story? (the HTML5 parser currently breaks an API that was introduced for Google Desktop)
19:04
<hsivonen>
oops wrong window