00:42
<MikeSmith>
Philip`: you still awake?
00:47
<Philip`>
MikeSmith: Yes
00:48
<MikeSmith>
Philip`: I'm getting an error from spec splitter, trying to figure out to fix it
00:48
<MikeSmith>
if e.getnext().tag == 'h2' and 'no-toc' not in (e.getnext().get('class') or '').split(' '):
00:48
<MikeSmith>
AttributeError: 'NoneType' object has no attribute 'tag'
00:48
<MikeSmith>
I have lxml 2.something installed
00:49
<MikeSmith>
2.1.3
00:55
<Philip`>
MikeSmith: What input are you using?
00:55
<MikeSmith>
my document-conformance draft
00:56
<Philip`>
Does it work if you run it with http://www.whatwg.org/specs/web-apps/current-work/source ?
00:57
<MikeSmith>
Philip`: trying now
00:58
<MikeSmith>
no, I get:
00:58
<MikeSmith>
del short_header[3:]
00:58
<MikeSmith>
TypeError: 'NoneType' object does not support item deletion
00:59
<MikeSmith>
hmm, though it does work if I run it on the "index" file (instead of the "source" file)
00:59
<Philip`>
MikeSmith: Oops
00:59
<Philip`>
I should have said index
00:59
<MikeSmith>
?
01:00
<MikeSmith>
yeah, index file works
01:01
<Philip`>
If it doesn't work on your document, I guess your document is insufficiently similar to HTML5
01:01
<Philip`>
but there's no kind of documentation or anything to describe what structure is expected
01:02
<Philip`>
For the original error you mentioned, it looks like that would only fail if it couldn't find an <h2> child of <body> that didn't have class=no-toc
01:07
<MikeSmith>
Philip`: OK
01:07
<MikeSmith>
Philip`: <h2> child of <body>, or <h2> descendant of <body>?
01:08
<MikeSmith>
oh
01:08
<Philip`>
MikeSmith: Child
01:08
<MikeSmith>
yeah, I see
01:09
<MikeSmith>
OK, I can see I'll need to mess around with it a bit to see if I can make it work with my doc
01:10
<Philip`>
It's not at all designed as a general purpose tool
01:10
<Philip`>
so it'll probably need various tweaks
01:11
<MikeSmith>
yep, I can see now from looking at the code.. But I don't think it'll be too much work to make the tweaks I need
01:24
<Hixie>
anyone seen aaronl recently?
01:25
<Hixie>
or know how to contact him?
02:05
<MikeSmith>
Hixie: Aaron Leventhal?
02:06
<Hixie>
yes
02:06
<MikeSmith>
you got his e-mail address?
07:27
<zcorpan_>
"While [noembed] can be positioned anywhere on the page, it is a good idea to include it as a child element of embed so that it is clear to assistive technologies that a text alternative is associated with the embed element it describes." -- http://www.w3.org/TR/2008/NOTE-WCAG20-TECHS-20081211/H46.html
07:29
<zcorpan_>
>Editorial Note: Is it true that noembed can go either beside or inside embed? Is there a preference?
07:29
<zcorpan_>
<embed> is an EMPTY element type, just like <img>. It can't have any contents. -- http://lists.w3.org/Archives/Public/public-comments-wcag20/2005Nov/0009.html
07:29
<heycam>
zcorpan_, and the point is the <embed> is an empty element, so can't have children?
07:29
<zcorpan_>
the point is they ignored my comment
07:29
<heycam>
:(
07:29
<heycam>
is that the final version of that document?
07:30
<zcorpan_>
yes, it's a REC now
07:30
<heycam>
that one you linked to is a NOTE though, so perhaps that can be updated easily
07:31
<zcorpan_>
maybe
08:59
<othermaciej>
this is a nice article: http://www.readwriteweb.com/archives/5_exciting_things_in_html_5.php
08:59
<othermaciej>
(which probably most here have seen already)
09:43
<jgraham>
gsnedders: pms.n should have the laetst anolis now
10:37
<jgraham>
Totally the wrong pklace to ask but does anyone have any ideas why I can't run Firefox 2 under Ubuntu 8.10 (it dies when trying to show the main window with an unhelpful X11 error; the profilemanager window appears fine)
10:48
<Lachy>
jgraham, is it possible the profile its using is corrupt in some way? have you tried creating a new profile and running it?
10:49
<Lachy>
usually, whenever I get Firefox crashing regularly, it's because there's something wrong with the profile
10:55
<Philip`>
My router's configuration interface says: <tr> <script language="javascript">document.write('<td onmouseover="this.style.backgroundColor='+mouseover+'" onmouseout="this.style.backgroundColor='+mouseout+'" onclick=parent.location.href="/status.stm">');</script> <a class="section" href="sindex.stm" target="main1"><p class=p1>Security</p></a> </td> </tr>
10:55
<Philip`>
which is fun
11:00
<Philip`>
Also it doesn't work in Opera - something to do with changing two frames' location simultaneously when you click causes it to not load sindex.stm (and therefore it's impossible to access the Security section)
11:03
<Lachy>
Philip`, please file a bug about that
11:04
Philip`
will have to try to produce a reproducible test case, and is too lazy to do that right now
11:07
<Lachy>
Philip`, just make your router config page publicly accessible and I could do that from here :-)
11:08
<Philip`>
Lachy: I would be happy to do that, but I can't get to the configuration page that lets me make it publicly accessible :-p
11:08
Philip`
will look at it later today anyway
12:29
<jgraham>
Lachy: Yes, I tried that
13:02
<Philip`>
Hmm, I can't work out how to reproduce the router's behaviour in Firefox
13:04
<Lachy>
is that because Firefox doesn't suffer from the same bug as Opera, or is it returning different pages to it or something?
13:06
<jgraham>
Lachy: Did you have an archive of the whole acid 3 test somewhere?
13:06
<Lachy>
jgraham, yeah, on Opera's t server
13:06
<Lachy>
I think that one might be a little out of date though.
13:07
<Philip`>
Lachy: I mean I'm trying to make a simplified test case based on the HTML that the router serves (to Firefox, but I don't think it varies between UAs), but it doesn't have the same behaviour in Firefox that the real router's HTML has
13:08
<Lachy>
jgraham, see t/core/standards/acid3/
13:08
<jgraham>
Lachy: Thanks
13:09
<Lachy>
jgraham, I'll update it now to the latest version. Just give me a few minutes
13:14
<Lachy>
jgraham, the test has been updated
13:28
<zcorpan>
http://software.hixie.ch/utilities/js/live-dom-viewer/?%3Cscript%3E%0Afor%20(var%20i%20%3D%201%3B%20i%20%3C%200xFFFF%3B%20%2B%2Bi)%0Atry%20%7B%0A%20eval(%22var%22%20%2B%20String.fromCharCode(i)%20%2B%20%22x%22%20%2B%20i%20%2B%20%22%3D%5C%22%5C%22%3Bw(x%22%20%2B%20i%20%2B%20%22%2B%22%20%2B%20i%20%2B%20%22)%22)%0A%7D%20catch(e)%20%7B%0A%7D%0A%3C%2Fscript%3E (may take long time to run)
13:31
<wilhelm_>
http://people.opera.com/wilhelmja/nested-form.html <- what is correct behaviour here? Firefox submits with both buttons. Opera does not.
13:33
<olliej>
wilhelm_: webkit appears to only submit on the first
13:33
<Lachy>
wilhelm_, Firefox 3 doesn't submit with the second button
13:33
<Lachy>
the reason is because of the way nested forms are parsed
13:33
<Lachy>
if you look at the DOM, you'll see that the second button isn't within the form
13:35
<Lachy>
wilhelm_, http://james.html5.org/cgi-bin/parsetree/parsetree.py?uri=http%3A%2F%2Fpeople.opera.com%2Fwilhelmja%2Fnested-form.html
13:36
<wilhelm_>
Indeed. Firefox did submit with both buttons a few changes ago, though. Looks like I reduced the test too much. (c:
13:36
wilhelm_
looks at it again.
13:40
<jgraham>
Hmm the HTML5 spec still defines the form elment pointer but doesn't seem to use it anywhere
13:42
<wilhelm_>
There. Reload and try again now. Firefox submits on button 2, Opera does not.
13:42
<wilhelm_>
(I removed a <div> too much :)
13:44
<olliej>
wilhelm_: webkit submits on both
13:45
<jgraham>
I guess IE submits on both?
13:47
<Lachy>
jgraham, yes, IE and Opera give the same results as each other, and Firefox and Webkit give the opposite result
13:47
<wilhelm_>
IE6 gives the same result as Opera.
13:48
<Lachy>
if the html5lib parse tree viewer is giving the correct result, then Opera matches HTML5.
13:49
<jgraham>
Lachy: I was more concerned that HTML5 might be wrong :)
13:49
<Lachy>
IE8's DOM includes the second submit button within the form, but still doesn't let it submit it
13:49
<jgraham>
If HTML5 matches IE then it seems OK
13:50
<Lachy>
IE's behaviour is buggy, so HTML5 shouldn't match it
13:50
<jgraham>
Lachy: Not IE8, IE6 (in this case)
13:50
<Lachy>
jgraham, oh, ok. I don't have IE6 to test with, so I don't know what it's result is
13:51
<wilhelm_>
Lachy: IE6 and IE7 do not submit #2.
13:53
<Lachy>
ok, that matches the IE8 result, and Opera, so that's good enough
13:54
<wilhelm_>
Yep. Answers my question. I was wondering if we were doing something wrong here. (c:
14:04
<zcorpan>
http://simon.html5.org/dump/ecmascript-whitespace.txt
15:36
<zcorpan>
hmm. a multiline comment in ecmascript is considered a linebreak for the purposes of semicolon insertion
15:36
<zcorpan>
although ie and webkit don't get that right
16:32
<Philip`>
http://www.readwriteweb.com/archives/5_exciting_things_in_html_5.php#comment-120375 - "It's possible to write in HTML5 now if you ignore IE's inabilty to render XML properly. I've wrote 3 sites in it now, http://ortatherox.com is a pretty good example."
16:32
<Philip`>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">; ... ... ... <section> <h1>Current projects:</h1><br/><br/> <projectdump> <article ...> <info ...> ... </info> <img .../> </article> <article ...> ...
16:32
<Philip`>
Hmm, that doesn't look quite right to me
16:40
<jgraham>
Philip`: About half the comments on that article appear to be utterly clueless
16:42
<Philip`>
jgraham: Only half? That's pretty good :-)
16:50
<jgraham>
Philip`: I don't think I said otherwise :)
17:00
<erlehmann>
well, firefox doesn't even display the <footer> element on my blog
17:01
<erlehmann>
comments ? the article is failing itself - code as graphics, yay !
17:02
<erlehmann>
because marking it up is SCIENCE
17:04
<erlehmann>
the table and pie chart relation is fun, though ;)
17:24
<gsnedders>
Hixie: yt?
19:19
<Hixie>
jgraham: the form element pointer is used
20:32
gsnedders
has Safari hang while trying to copy too much, and loses a draft post
21:51
<Hixie>
jgraham: yt?
21:52
<Hixie>
nm