00:28
<Hixie>
wtf, sort(1) just decided my locale had changed
00:45
<annevk>
that sounds kind of weird
01:32
<heycam>
hopefully not mid-sort...
01:39
<annevk5>
heycam, btw, I found one more problem with putting event handlers into DOM Core
01:40
<heycam>
oh yes?
01:40
<annevk5>
heycam, if you look at the bits where it sets scope for content attributes it references the HTML form element
01:40
<annevk5>
heycam, as well as defaulting to the Window object or some such
01:40
<heycam>
bah
01:41
<annevk5>
yeah, maybe just the IDL attributes ought to be moved
01:41
<annevk5>
and languages define content attributes themselves and how they map for now
01:41
<heycam>
ok, it's not too much work
01:41
<heycam>
you can have a hook for that in DOM Core for simple ones
04:05
<Hixie>
i do believe hober volunteered to spec innerText
04:05
<Hixie>
:-P
14:57
<annevk>
Did we ever consider standardizing the contains() method?
14:57
<annevk>
I cannot find it in hg log
14:57
<annevk>
Gecko does not have it, but Presto/WebKit/Trident do
14:58
<annevk>
boolean = Element.contains(Element)
15:02
<Ms2ger>
Never heard of
15:33
<The_8472>
annevk, is that about layout or dom traversal?
15:34
<annevk>
traversal
15:34
<annevk>
I wonder where the actual code for that method is located in WebKit
15:34
<The_8472>
then you can just iterate over the parents... it's just a few lines of code.
15:35
<annevk>
sure or you can use compareDocumentPosition
15:38
<bga_>
annevk you can standardtize _commonMinParent(node1, node2) because via Range API its so slow and look like hack
15:39
<annevk>
I'm not sure what you mean
15:41
<bga_>
get 2 nodes and find min parent node that contains given 2 nodes
15:41
<bga_>
min parent, not documentElement
15:41
<annevk>
and why do you want this?
15:45
<bga_>
annevk i can move parent <ul> by 2 given <li> even if one <li> is is deep inside
15:47
<bga_>
btw this operation can be generalized to many input nodes
15:51
<The_8472>
getNearestCommonAncestor would be a better name i think
15:52
<bga_>
yeah
18:44
gsnedders
wishes there was an IRC channel where JS people lurked
20:29
<mhausenblas>
gsnedders: re 'wish there was an IRC channel where JS people lurked' - I'd give #Node.js a try ;)
20:30
<gsnedders>
mhausenblas: Probably rather bias towards V8. :)
20:30
<mhausenblas>
oh well :P
20:30
<mhausenblas>
seems rather busy there tbh
20:31
<mhausenblas>
anyways ... /me back to https://github.com/mhausenblas/web.instata
20:31
<gsnedders>
(Node.js is based on V8, so, well, yeah.)
20:31
<mhausenblas>
sure
20:31
<mhausenblas>
but my impression was that quite some JS people hang out there
20:32
<mhausenblas>
laters
22:19
<jgraham>
Surely HTML5 doesn't really use "child" to mean "descendant"
22:31
<foolip_>
jgraham, [citation needed]
23:04
<charlvn>
jgraham: example?
23:05
<Dashiva>
hsivonen: A few days late, but my guess is a lot of people still use firefox 3.6 because of ubuntu
23:06
<charlvn>
Dashiva: why because of ubuntu?
23:10
<Dashiva>
Because the current LTS is lucid with 3.6
23:11
<charlvn>
not sure if this is typical but most ubuntu users i know upgrade rapidly to newer versions
23:11
<charlvn>
people only seem to care about lts for servers
23:12
<Dashiva>
Well, there's probably a similar thing going on debian too
23:12
<charlvn>
well debian uses iceweazel
23:20
<jgraham>
foolip_: http://www.w3.org/Bugs/Public/show_bug.cgi?id=13480
23:21
<foolip_>
I wonder if we're supposed to be reading/filing spec bugs on Saturday nights...
23:22
<charlvn>
bug with no references in spec = fail