00:12
<Philip`>
zcorpan: "<map name> works in all except in Gecko in XHTML and WebKit in XHTML." - but the table's data for 007 seems to indicate it does work in WebKit-XHTML
00:13
<zcorpan>
Philip`: ah, yes, thanks
00:23
zcorpan
likes the "no alt = image is meaningful" idea
00:38
<jgraham>
http://wordsandpictures.dyndns.org/html5/parsetree.html (a HTML5 DOM viewer based on html5lib -- still very rough)
00:39
jgraham
is going to sleep now
00:40
<zcorpan>
jgraham: nice!
00:40
<zcorpan>
why are the elements uppercased?
00:42
<jgraham>
Ah, in innerHTML view they shouldn't be... I'll remove that CSS :)
00:42
<zcorpan>
it shouldn't be in the tree either, should it?
00:44
<jgraham>
I guess it makes more sense to have everything lowercase (it's also easier)
00:44
<zcorpan>
yeah
00:49
<zcorpan>
innerHTML view says "<!DOCTYPE: HTML>"
00:52
<zcorpan>
perhaps the textarea should be POST?
00:53
zcorpan
stops bugging jgraham now
01:05
<Lachy>
jgraham, #text nodes shouldn't appear outside of the root element.
01:08
<zcorpan>
Lachy: i think they should
01:08
<zcorpan>
(per spec that is)
01:09
<zcorpan>
(if the spec is wrong is another matter)
01:09
<Lachy>
I mean in the DOM view
01:10
<zcorpan>
yes?
01:10
<Lachy>
so the DOM spec applies
01:10
<Lachy>
and I'm fairly sure they shouldn't
01:10
<zcorpan>
the html5 parsing spec says to append text nodes to the Document object in some cases
01:11
<Lachy>
that's weird
01:13
<zcorpan>
what would you do with whitespace between the doctype and the first tag?
01:13
<Lachy>
drop it
01:13
<zcorpan>
why?
01:13
<Lachy>
outside of the document, it has no meaning and irrelevant
01:14
<Lachy>
s/document/root/
01:14
<Lachy>
that's what browsers do
01:14
<zcorpan>
i think at least firefox appends the whitespace to the HEAD instead
01:15
<zcorpan>
not sure about the others
01:16
<zcorpan>
and whitespace after </body> and </html> is appended to the body or whatever unclosed element was open in body... in firefox, and iirc
01:19
<zcorpan>
i don't feel strongly about it either way, but the way it's defined now preserves the "source code" after parsing and serializing (fwiw)
01:20
<Lachy>
firefox doesn't retain whitespace before the root
01:23
<zcorpan>
Lachy: compare data:text/html,<!doctype html>%0A<html> and data:text/html,<!doctype html><html> in DOM viewer (check the contents of HEAD)
01:24
<zcorpan>
the first has a text node in HEAD, the second doesn't
01:25
<Lachy>
which version of FF are you using?
01:25
<annevk>
morning
01:25
<Lachy>
hi annevk
01:25
<zcorpan>
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a4pre) Gecko/20070417 Minefield/3.0a4pre
01:25
<Lachy>
I've only got FF2
01:25
<zcorpan>
got the same results last time i checked, which was probably a year ago or something
01:25
<Lachy>
and it doesn't show the whitespace
01:25
<zcorpan>
really?
01:25
<annevk>
testing parsing?
01:26
<zcorpan>
annevk: yeah
01:26
<Lachy>
testing how whitespace outside of the root should be handled
01:26
<zcorpan>
whitespace between doctype and root
01:26
<annevk>
it would make sense to contribute to the testsuite format already developed for parsing I think
01:26
<Lachy>
annevk, see http://wordsandpictures.dyndns.org/html5/parsetree.html
01:27
<annevk>
fancy
01:27
<annevk>
what I meant was that there's already a testsuite input and output format
01:28
<annevk>
through some scripting that can be used for browser testsuites etc.
01:28
annevk
slowly fetches 208 e-mails
01:29
<zcorpan>
Lachy: tested in fx2 now and indeed it gets dropped
01:30
<Lachy>
annevk, where have you gone touring around so far? Been to the rainforest yet?
01:31
<Lachy>
or sand surfing?
01:31
<annevk>
heh, all public-uwa messages get marked as spam
01:31
<annevk>
Lachy, I've been doing the rainforest walk
01:31
<annevk>
yesterday
01:31
<annevk>
it was quite exhausting
01:31
<annevk>
we walked over 20km
01:32
<annevk>
after about 12km rainforest we found some water
01:32
<annevk>
after 20km we found a beer and some chips :)
01:32
<Lachy>
:-)
01:32
<Lachy>
who did you go with?
01:32
<annevk>
the plan was to take a short walk of about an hour
01:33
<annevk>
but we missed something underway...
01:33
<annevk>
with marcos
01:34
<zcorpan>
data:text/html,%3Cp%3Ex%3C%2Fbody%3E%20%3C%21--foo--%3E%20%3C%2Fhtml%3E%20%3C%21--bar--%3E%20x
01:34
<Lachy>
jgraham, test FF3 with XML to see if it keeps whitespace outside of the root
01:35
<annevk>
that's conforming btw
01:35
<annevk>
and should be done per XML
01:35
<annevk>
Opera should have some fix for that for the next major Opera release
01:37
<zcorpan>
Lachy: fx3 drops whitespace outside root in xml
01:37
<Lachy>
right
01:37
<annevk>
dropping?!
01:38
<annevk>
it's simply not added per the XML grammar
01:38
<zcorpan>
what's the difference?
01:40
<zcorpan>
annevk: did you see http://xhtml.se/2007/04/20/im-not-arguing-im-just-making-fun-of-them/ ?
01:43
<Dashiva>
I'm famous!
01:43
<zcorpan>
lol
01:44
<annevk>
no
01:45
<Dashiva>
How come I'm the only one with "" around my name?
01:45
<annevk>
lol
01:46
<Lachy>
probably because he thinks that's not your real name
01:46
<Dashiva>
Unlike zcorpan? :)
01:46
<zcorpan>
:D
01:46
<zcorpan>
it is! promise!
01:46
<Lachy>
:-)
01:47
<Dashiva>
What's the status of that 'conformant html5' image?
01:47
<zcorpan>
?
01:48
<Lachy>
do you mean the Valid HTML5 logo with Hixie's cat on it?
01:48
<Dashiva>
Yeah, that one
01:48
<zcorpan>
ah
01:48
<zcorpan>
http://simon.html5.org/temp/valid-html5.png
01:48
<annevk>
you should move that out of temp
01:49
<Dashiva>
Is valid the right word? Is using the cat legal? How many submarine patents are expected?
01:49
<Lachy>
ha!
01:49
<zcorpan>
ftp doesn't work for me today
01:49
<zcorpan>
Dashiva: cat used without permission :)
01:50
zcorpan
expects to get sued by Hixie
01:50
<annevk>
whoa
01:50
<Lachy>
permission from Hixie is implied, he hasn't complained about it
01:50
<annevk>
dhyatt has enough time to be co-editor
01:50
<Lachy>
probably just enough time to keep those who think we need 2 editors happy
01:51
<Dashiva>
Hixie can send him some diffs so Hyatt can commit them
01:51
<zcorpan>
heh
01:52
<Lachy>
why is http://simon.html5.org/temp/ forbidden? I want to see what other cool stuff you have hidden in there
01:52
<annevk>
it's temp
01:52
<Lachy>
so?
01:52
<Dashiva>
temp stuff shouldn't be accessible, it leads to people linking it and expecting permanence
01:52
<zcorpan>
don't have cool stuff there
01:54
<zcorpan>
http://simon.html5.org/temp/program my gym program from last year, just started with it again now
01:54
<zcorpan>
in swedish
01:56
<zcorpan>
http://simon.html5.org/temp/browsers/ icons used in the web-apps-tracker
01:56
<annevk>
heh, collegue of dhyatt proposes dhyatt and then people wonder whether dhyatt actually agreed to it...
01:56
<annevk>
i suppose it's possible he didn't...
01:57
<zcorpan>
not when the mail proposing it says "he has said he's willing to do it"
01:58
<annevk>
oh right
01:58
<annevk>
guess that tells how closely I read some of my e-mail initially
02:26
<zcorpan>
Lachy: http://www.google.com/search?q=site%3Asimon.html5.org%2Ftemp should bring up anything "cool" i've hidden there :)
02:26
Dashiva
links to hsivonen's checker using valid-html5 image. Go precedent!
02:26
zcorpan
doesn't think that's a good idea
02:26
<Lachy>
why not?
02:27
<Dashiva>
"Some markup validation/checking services give out a small badge for advertising that a document passed. This service does not."
02:28
<zcorpan>
stickies linking to a checker generally gives the impression that the checker result is some sort of status indicator
02:29
<zcorpan>
the valid html5 image was mostly a joke on my part and i think hsivonen wants his tool to be a QA tool, not a status indicator
02:29
<annevk>
ooh, security
02:30
<Dashiva>
I fully agree, but that doesn't stop me from being subversive
02:31
<zcorpan>
fair enough :)
02:32
<zcorpan>
although i'd suggest that the link point to whatwg.org/html5 if anything
02:32
annevk
wonders when Web Forms 2 will be merged with HTML5
02:34
<zcorpan>
Dashiva: also see first paragraph in (4) in http://lists.w3.org/Archives/Public/public-html/2007JanMar/0433.html
02:35
<Dashiva>
I think the page is valid pretty much anything in its current state
02:36
<Dashiva>
Well, the <img> tag doesn't have the / needed for xhtml
02:36
<annevk>
<img> can also be <img></img> in XHTML
02:36
<annevk>
fwiw
03:00
<annevk>
http://www.w3.org/mid/op.tq008yhnsmjzpq⊙al
03:02
<annevk>
http://therealcrisp.xs4all.nl/blog/2007/04/22/html5-microsoft-and-the-opt-in-catch/
03:03
<annevk>
http://labs.google.com/goog411/
03:18
<annevk>
+ <h4>Origin</h4>
03:18
<annevk>
+ <!-- Hallowed are the Ori -->
03:18
<annevk>
heh
03:25
<Lachy>
annevk, which page had that ori comment in it?
03:26
<annevk>
HTML5?
03:26
<annevk>
Hixie defined origin for scripts
03:33
<Lachy>
That solution on crisp's blog won't work as-is, we tried it already
03:34
<Lachy>
Though, my latest response from Chris (off list) indicates that he'd listen to a solution that starts out as an opt-in and can transition to an opt-out, once the dependence on opt-ins isn't required
03:35
<zcorpan>
i do think making [if IE] return false in ie8 would help them not breaking things, but he didn't reply to that suggestion. perhaps i should bug him about that again
03:35
<annevk>
it requires too many fixes
03:35
<annevk>
in one go
03:36
<zcorpan>
then in ie9
03:36
<annevk>
if we got the proper testsuites ready by then...
03:36
zcorpan
will be working on that this summer
03:37
<Lachy>
I think the only way we're going to get Chris to compromise is to make HTML4/XHTML1 DOCTYPEs require an opt-in, and use the change in DOCTYPE in HTML to convert to an opt-out system
03:38
<annevk>
we shouldn't have to do much
03:38
<annevk>
this would only apply to IE
03:38
<annevk>
i hope
03:38
<Lachy>
that way, IE can use the time it takes to transition from HTML4/XHTML1 to HTML5 to improve its standards support and get to a point where it's close enough to interop with outhers, to not require an explicit opt-in
03:38
<Lachy>
yes, it would be an IE only opt-in/out
03:39
<annevk>
personally I want to keep fixing quirks mode, documenting quirks, etc.
03:39
<Lachy>
yeah, that would be good, but there's no chance IE is going to change it's quirks mode at all
03:40
<zcorpan>
in any case, it should be possible for authors to trigger a "latest standards mode", author against opera/firefox/safari, then work around bugs in current IEs without making assumptions about IE.next
03:40
<zcorpan>
annevk: yeah, me too
03:45
annevk
wonders if http://dev.w3.org/cvsweb/~checkout~/2006/waf/widgets/Overview.html?content-type=text/html;%20charset=utf-8#autodiscovery is good enough to define a new link type
03:47
zcorpan
thinks it is
03:48
<zcorpan>
or how is it handled today in opera?
03:48
<Lachy>
annevk, typo: "...to create an hyperlink" s/an/a/
03:50
<zcorpan>
ah, Content-Type: application/x-opera-widgets
03:51
<annevk>
I'm pretty sure it's always an before h...
03:51
<Lachy>
no
03:51
<zcorpan>
depends on how it's pronounced
03:51
<zcorpan>
an hour
03:51
<Lachy>
it doesn't depend on the letter, it depends on the sound
03:53
<annevk>
yeah nm me
03:54
<zcorpan>
annevk: if there is application/widget, why is there a need for rel="widget"?
03:54
<zcorpan>
surely the opera widget page works fine with only the mime type
03:55
<Lachy>
same reason there is rel=feed
03:55
<zcorpan>
for UI?
03:55
<Lachy>
the rel allows the UA to detect the widget before fetching it and offer a better UI
03:56
<zcorpan>
ok
03:56
<annevk>
right
04:04
<annevk>
fixed the typo and some other stuff fwiw
04:06
<annevk>
might be back later... food
04:39
<Hixie>
anyone got any pet bugs in browsers that they'd want fixed? any bugs. any browsers.
04:39
<Hixie>
ideally a DOM2 or HTML4 bug, maybe CSS2.1
04:39
<Hixie>
or JavaScript
04:42
<Lachy>
I want to see display: table-* properties fixed to work with less bugs in FF
04:43
zcorpan
points to http://simon.html5.org/test/ie7b2-bugs/
04:43
Hixie
takes notes
04:44
<Hixie>
Lachy: any specifics in mind?
04:44
<Hixie>
zcorpan: wow cool thanks
04:44
<zcorpan>
np
04:45
<Lachy>
see my site in FF. Sometimes the columns don't work properly, but can usually be fixed by reloading
04:46
<zcorpan>
Lachy: oh yeah i get that too on some layouts
04:46
<zcorpan>
very unpredictable
04:46
<Hixie>
weird
04:46
<Hixie>
http://simon.html5.org/test/ie7b2-bugs/003.html <-- wtf is IE doing here
04:47
<Lachy>
also, if you create elements with JS and insert them into the DOM with display: table-cell; applied, it doesn't work well either
04:47
<zcorpan>
Hixie: no idea
04:47
<Lachy>
I'll create a test case
04:49
<zcorpan>
Hixie: also http://simon.html5.org/test/opera/
04:49
<Hixie>
cool, more tests
04:52
<Lachy>
http://software.hixie.ch/utilities/js/live-dom-viewer/?%3C%21DOCTYPE%20html%3E%0A%3Cstyle%3E%0Adiv%20%7B%20display%3A%20table-cell%3B%20border%3A%201px%20solid%20blue%3B%20%7D%0A%3C/style%3E%0A%3Cp%3EThese%20columns%20are%20in%20the%20markup%3A%0A%3Cdiv%3Ecolumn1%3C/div%3E%0A%3Cdiv%3Ecolumn2%3C/div%3E%0A%3Cdiv%3Ecolumn3%3C/div%3E%0A%0A%3Cp%3EThese%20columns%20are%20created%20by%20a%20script%3A%0A%0A%3Cscript%3E%0Avar%20div%3B%0Afor%20%28va
04:52
<Lachy>
r%20i%20%3D%201%3B%20i%20%3C%3D%203%3B%20i++%29%20%7B%0A%20%20div%20%3D%20document.createElement%28%22div%22%29%3B%0A%20%20div.innerHTML%20%3D%20%22column%20%22%20+%20i%3B%0A%20%20document.body.appendChild%28div%29%3B%0A%7D%0A%3C/script%3E%0A
04:52
<Hixie>
hit the upload link
04:52
<Lachy>
I uploaded that to the DOM viewer clipboard, so you can just download it
04:52
<Hixie>
cool
04:52
<Hixie>
got it
04:57
annevk
wouldn't mind interop on feature "x"
04:58
<Hixie>
any specifics in mind?
04:59
<annevk>
innerHTML
04:59
<annevk>
HTML table model
04:59
<Hixie>
zcorpan: these are really good tests
04:59
<zcorpan>
:)
05:00
<annevk>
heh, why do you think we hired him?
05:00
annevk
doesn't have much tests for either of his suggestions
05:03
<annevk>
what are the feature requests for?
05:04
annevk
wonders why Opera doesn't do the dynamically generated <div> stuff correctly
05:05
<annevk>
ooh, Firefox has problems too
05:05
<Lachy>
annevk, are you talking about the test I made? What does opera get wrong?
05:05
<annevk>
some build i have doesn't render the generated divs at all
05:05
<zcorpan>
same here
05:06
<annevk>
actually, all builds so far...
05:06
<Hixie>
i'm preparing for the writing of acid3
05:06
<Lachy>
that's weird. It renders them as soon as I click download, but they disappear after the source is edited
05:06
<Hixie>
trying to get bugs lined up
05:06
<annevk>
(this would be covered by my "HTML table model" suggestion above which really should be named "HTML table layout model")
05:06
<Lachy>
oh, awesome!
05:07
<Hixie>
especially interested in DOM tests
05:07
<Hixie>
and JS
05:07
<Lachy>
when do you expect acid3 to be released?
05:08
<Hixie>
when it's ready
05:08
<Lachy>
fair enough
05:08
<Hixie>
http://hixie.ch/www/tests/evil/acid/003/ is where things will happen at first
05:08
<annevk>
http://tc.labs.opera.com/html/canvas/getContext/2d/ still shows quite some differences between browsers
05:08
<annevk>
although I suppose <canvas> may be too new
05:09
<Hixie>
yeah this is going to cover only things that were specced around 2003 or earlier
05:09
<annevk>
k
05:09
<annevk>
"PNG that contains some HTML"?!
05:10
<annevk>
IE still has a bunch of CSS parsing issues
05:11
<annevk>
http://annevankesteren.nl/2007/02/ie7-css-hacks contains a list of copy & paste testcases
05:12
<annevk>
oh, \n\r in document.write() and scripts in general might be good
05:12
<annevk>
or \r\n whatever it is
05:13
<Hixie>
has to be only things that can be seriously argued out of existing specs, unfortunately
05:15
<zcorpan>
having ie support the events model correctly would be nice, i think... and addEventListener, event.target, etc.
05:15
<Hixie>
yeah, gonna test that for sure
05:15
<annevk>
handling of <i><b></i> is to new too?
05:15
<annevk>
or is it too new too?
05:16
<Lachy>
I didn't realise FF3 passed acid2 already. That's awesome! :-)
05:16
<Hixie>
parsing of html is too new if it's error handling
05:16
<Hixie>
Lachy: yeah, hence it being time for acid3
05:16
<zcorpan>
Lachy: better late than never :)
05:18
<zcorpan>
getAttribute("for") in IE
05:18
<Lachy>
Hixie, add this: <!--[if IE]>FAIL<![endif]--> :-)
05:18
<zcorpan>
(IE needs getAttribute("htmlFor"))
05:19
<Lachy>
same for "className"
05:19
<zcorpan>
yeah
05:19
<annevk>
<style type="">
05:19
<Lachy>
and there's something else too
05:19
Lachy
checking the DOM ref...
05:19
<annevk>
versus <style type="unknown"> versus <style> versus <style type="text/css">
05:20
<annevk>
maybe in the CSSOM? for float? which becomes .cssFloat as attribute
05:20
<Lachy>
I think getAttribute("http-equiv"); also has the problem
05:20
<zcorpan>
likely
05:21
<zcorpan>
using getAttribute on event handler attributes doesn't work right either iirc
05:21
<annevk>
events on body / document / window
05:23
<Lachy>
event object isn't passed to the handler in IE, needs window.event
05:23
<annevk>
already mentioned
05:23
<Lachy>
oh, sorry
05:25
<Lachy>
http://developer.mozilla.org/en/docs/Core_JavaScript_1.5_Reference:Global_Objects:Array#Methods some of those aren't supported in IE
05:25
<annevk>
i suppose investigating in what Dean Edwards has to work around in his library might give some good suggestions on to what to include
05:26
<Lachy>
I assume you'll test the NS methods in the DOM too?
05:27
<Hixie>
already looked at dean's stuff
05:27
<Hixie>
nah, no point testing namespaces really
05:27
<Lachy>
ok
05:27
<Hixie>
since we don't particularly want anyone to use them
05:27
<Lachy>
alright
05:28
<annevk>
nasty SVG bits?
05:31
<Lachy>
Hixie, <link rel="icon"> - IE uses rel="shortcut icon"
05:32
<Lachy>
although, technically it wasn't specified till recently, icons have been widely supported for a while
05:37
<Hixie>
yeah but there's no spec that says it has to be "icon"
05:38
<Lachy>
I suppose you're not counting HTML5 then?
05:38
<annevk>
before 2003
05:38
<annevk>
HTML5 _started_ in 2004
05:38
<Lachy>
I know that, but it's been widely supported for much longer than that
05:38
<annevk>
the other requirement is for it to be in a spec
05:39
<Hixie>
unless i can point at a REC with clear conformance criteria, it doesn't count
05:39
<Lachy>
ok
05:39
<Hixie>
since you can argue that it isn't required for compliance
05:39
<annevk>
that leaves out testing HTML features :p
05:44
<Hixie>
mostly, yeah
05:45
<virtuelv_>
One thing that definetly would need to go into acid3 is how 'apply' works
05:46
<Hixie>
which spec?
05:46
<Lachy>
virtuelv_, in JavaScript?
05:46
<virtuelv_>
Lachy: yup
05:46
<virtuelv_>
I've run into cases where the behavior is rather exotic across browser
05:47
<virtuelv_>
+s
05:47
<Lachy>
is it defined in ECMA 262?
05:49
<virtuelv_>
iirc, yes
05:49
<virtuelv_>
lemme check, though
05:49
<Lachy>
yep, it's on page 87 (section 15.3.4.3
05:50
<Hixie>
if you can give me a testcase and explain how it tests behaviour described in the spec i can add it, sure
05:52
<Hixie>
anne, wouldn't rel=widget be better as a type="" value?
05:52
<annevk>
similar to rel=feed
05:53
<Lachy>
Hixie, why?
05:53
<virtuelv_>
Hixie: will do, bug me at the end of the coming week
05:53
<Hixie>
virtuelv_: k
05:53
<Lachy>
rel=widget is easier for authors to type and remember, compared with MIME types
05:53
<Hixie>
i guess
05:54
<virtuelv_>
inability to add stuff to the Element prototype is also, IMHO one thing browsers should get right in 2007
05:55
<virtuelv_>
s/in//
05:55
<Hixie>
unfortunately prototypes for elements aren't defined anywhere (yet)
05:56
<Hixie>
so that's not a standards compliance issues
05:56
<Hixie>
issue
05:56
<annevk>
It's more consistent with rel=stylesheet rel=feed etc. too. It means that authors have to learn one less trick (the trick that type= might lead to special handling too).
05:56
<Lachy>
but Elements are just Objects in ECMAScript, and Object is defined
05:56
<virtuelv_>
Hixie: that's rather unfortunate, really
05:57
<Hixie>
Lachy: if you can find a spec that says that, let me know :-)
05:57
<Lachy>
http://www.w3.org/TR/DOM-Level-2-Core/ecma-script-binding.html binds all the DOM objects to Object in ECMAScript
05:58
<Lachy>
ECMA 262 defines .prototype
05:58
<Lachy>
and it's how all other major browsers implement it, AFAIK
05:59
<Hixie>
but where does it say that the object has to have a prototype?
06:00
<virtuelv_>
Hixie: all objects that have constructors must have a prototype
06:00
<Hixie>
but Element doesn't have a constructor
06:02
<virtuelv_>
sigh. Neither does Node
06:02
<Lachy>
all Objects have constructors though. It inherits from Object, and so it has a constructor. It's just not available to scripts
06:06
<annevk>
but that Element is available somewhere in the global scope as attribute is also not defined
06:12
<Lachy>
border-collapse should be tested too (or was it tested in acid2 already?) http://lachy.id.au/dev/css/tests/bordercollapse/bordercollapse.html
06:13
<Lachy>
I think IE is the only one to fail those tests
06:14
<Hixie>
not really interested in css
06:14
<Lachy>
ok
06:15
<annevk>
location.hash when the page contains a single # is sometimes a compat issue iirc
06:15
<annevk>
oh, nm
06:16
<Hixie>
location was specced post 2003
06:16
<Hixie>
namely, last week
06:16
annevk
was under the illusion location was somehow part of old dom specs
06:16
<annevk>
did you and Maciej agree that the Window spec will be merged into HTML5?
06:31
<Lachy>
OMG WTF? "Long release cycles are a very good thing" on public-html
06:32
<annevk>
citing IE6 as an example
06:32
<Lachy>
Frequent releases of increasingly buggy browsers may be a bad thing, but the quicker we can get more standards compliant browsers into the market the better
06:56
<Hixie>
annevk: haven't asked
06:57
<annevk>
k
06:57
<Hixie>
annevk: but since Window was no longer being developped, and I needed to spec things that depended on it...
06:57
<annevk>
yeah, just wondering
06:58
<annevk>
now the chairs sort of "accepted" HTML5 will you merge in WF2? or let dhyatt do it? :p
07:06
<Hixie>
they have?
07:08
<Lachy>
Hixie, Chris responded fairly positively about the HTML5 spec
07:09
<Hixie>
uri?
07:09
<Lachy>
http://www.w3.org/mid/5C276AFCCD083E4F94BD5C2DA883F05A27D9CDDC38⊙twwnmc
07:12
<annevk>
whoa, schepers is asking for a third editor...
07:12
<Lachy>
annevk, I was just typing the same thing :-)
07:13
<Lachy>
2 editors is more than enough
07:15
<Hixie>
Lachy: it wasn't clear to me that he was accepting the proposal maciej put forward exactly. but yeah, that was positive regarding the spec itself.
07:15
<Hixie>
(my reply was http://lists.w3.org/Archives/Public/public-html/2007Apr/1241.html)
07:16
<Hixie>
i'm curious as to what people think "editor" means
07:17
<Hixie>
why does it matter what the opinions of the editor are?
07:17
<Lachy>
yeah, I don't understand why he wants the whatwg to stop either
07:18
<Hixie>
chris?
07:18
<Lachy>
yes
07:22
<Lachy>
I have no idea how I should respond to this about selectors API http://lists.w3.org/Archives/Public/public-webapi/2007Apr/0025.html
07:22
<Lachy>
I already said it's not wise to explicitly introduce undefined behaviour
07:24
<annevk>
Does anyone know what the last dot http://www.w3.org./ can possibly do?
07:25
<Hixie>
Lachy: well, what you have now doesn't guarentee interop, so what they're asking for doesn't really change that
07:25
<Hixie>
annevk: guarentees you're not going to do local dns lookup (with a suffix, e.g.)
07:25
<annevk>
yeah, just say that authors should not assume a specific prefix invocation algorithm or something
07:25
<Hixie>
bit like the leading / in /foo/bar
07:26
<Hixie>
saying authors "should not" is just a waste of time :-)
07:26
<Hixie>
won't do anything
07:26
<Hixie>
especially for APIs
07:26
<annevk>
should create a side-effect resolver...
07:26
<Lachy>
but I don't see what problems it solves by me taking it out
07:27
<annevk>
it makes things simpler
07:27
<Lachy>
so you think I should?
07:27
<annevk>
well, i was convinced
07:27
<annevk>
so yes
07:28
<annevk>
it's unfortunate jonas is so late with catching up with e-mail otherwise I would have fixed this ages ago (or never specced it)
07:29
<Lachy>
I suppose it doesn't really help authors much knowing their function is only going to be invoked once per prefix either
07:30
<annevk>
i suppose it's nice to point it out in interop concerns so people who are designing something similar know what to do
07:31
<annevk>
(same for people who wonder why it differs between browsers)
07:40
<Hixie>
annevk: "the ToASCII algorithm must apply successfully (without errors)"
07:40
<Hixie>
how can it fail?
08:13
<Lachy>
Hixie, this has a good list of IE bugs you could add to acid3 http://easy-designs.stikipad.com/ie-next-wishlist
08:15
<Hixie>
IE bugs are easy to find :-)
08:15
<Hixie>
it's other browsers that are the problem
08:16
<Lachy>
right
08:16
<Hixie>
in fact, i've added all of _one_ test to the page so far and it breaks in IE drastically.
08:17
<Lachy>
yeah, I saw that.
08:17
<Lachy>
I don't understand what causes it to break though
08:18
<Lachy>
is it because there's no font-size specified for body?
08:19
<Hixie>
i'm guessing it doesn't support inline-block
08:19
<Hixie>
though i thought it did
08:20
<Lachy>
it does for inline level elements only
08:22
<Lachy>
do you have some sort of plan for the final rendering, or are you just making it up as you go?
08:27
<Hixie>
it'll look mostly like it does now in firefox
08:27
<Hixie>
but i'm making it up as i go along
08:27
<Hixie>
and i want to add animation
08:37
<Hixie>
why is opera not using arial
08:37
<Hixie>
wtf
08:40
<Lachy>
heh, I keep forgetting to switch to FF3 when looking at test cases :-)
08:41
<Lachy>
maybe opera doesn't support :root
08:42
<Hixie>
seems unlikely
08:42
<Hixie>
but maybe
09:06
<Hixie>
last chance to see what the test is intended to look like before i break it
09:06
<Hixie>
http://www.hixie.ch/tests/evil/acid/003/index.html
09:06
<Lachy>
yeah, I just looked at it. It looks ok
09:07
<Hixie>
it already shows bugs in every browser except firefox
09:07
<Hixie>
and the only reason it works in firefox is i changed 'document' to 'window'
09:07
<Hixie>
for hte load event
09:07
<Lachy>
are you going to change it back to document?
09:07
<Hixie>
yes
09:07
<Hixie>
there's no window in 2003 standards
09:08
<Lachy>
yeah
10:46
<Hixie>
http://www.hixie.ch/tests/evil/acid/003/ and http://www.hixie.ch/tests/evil/acid/003/reference.html
10:46
<Hixie>
should look the same everywhere
10:46
<Hixie>
i haven't even tried adding tests yet and they don't
10:46
Lachy
checks every browser he has...
10:48
<Lachy>
nice, FF3 gets it right :-)
10:48
<Hixie>
it does?
10:48
<Lachy>
it did a second ago, not now
10:48
<Hixie>
i just get 0%
10:48
<Hixie>
oh you probably tested it before i switched it back to document
10:48
<Lachy>
yeah
10:49
<Hixie>
the reference rendering should be pixel-perfect, including font rasterisation
10:50
<Hixie>
but really the reference rendering is a test on to its own
10:50
<Lachy>
Opera 9 is doing surprisingly poorly
10:51
<Hixie>
opera 9 is hitting two bugs that i know of
10:51
<Hixie>
one, it's getting screwed by not having a <head> in the DOM, because one of the selectors goes through the <head>
10:51
<Hixie>
and two, it doesn't seem to do :root
10:53
Hixie
throws in some :first-child/:last-child tests
10:53
<Lachy>
which selector goes through head?
10:53
<Hixie>
*:first-child + * > * > p
10:53
<Hixie>
that's equivalent to head + body > div > p
10:53
<Lachy>
ah, I see
10:54
<Hixie>
as in, the only ps that it matches will match because the first simple selector there matches the head
10:54
<Hixie>
and since opera has no head...
10:57
<Hixie>
anyway i should go to bed
10:57
<Hixie>
nn
10:57
<Lachy>
cya
12:18
<gsnedders>
anyone know what percentage of XHTML docs are served as XML?
12:18
<gsnedders>
well, per-mille may be more useful, actually :P
14:25
<zcorpan>
Hixie: acid2 was easier to see if it was correct or not (without looking at the reference rendering)
14:31
<hasather>
zcorpan: agreed
14:31
<Lachy>
zcorpan, any suggestions for a better picture?
14:32
<hsivonen>
what test are you talking about?
14:32
<Lachy>
acid 3
14:32
<Lachy>
http://www.hixie.ch/tests/evil/acid/003/
14:32
<Lachy>
it's still a work in progress though
14:34
<zcorpan>
Lachy: hm, dunno... a questionmark inside a circle?
14:34
zcorpan
hides
14:34
<Lachy>
I thought maybe a cat
14:53
<zcorpan>
"Awareness of future trends." ?
15:02
<hsivonen>
zcorpan: indeed
15:07
<hsivonen>
It'll be interesting to see the diff for Web Apps 1.0 from the day the HTML WG was announced to the day the WG accepts HTML5 as the starting point (assuming that happens)
15:16
<SpookyET>
Opera allready supports some of it according to Wikipedia.
15:18
<Lachy>
SpookyET, yes, it has support for Web Forms 2.0 and a few things from Web Apps 1.0 like <canvas> and <event-source>
15:21
<hsivonen>
SpookyET: I meant it'll be interesting to see how much real work Hixie and the folks on the WHATWG list got done while public-html generated heat
15:25
<SpookyET>
hsivonen: http://en.wikipedia.org/wiki/Comparison_of_layout_engines_(WHATWG)
15:25
<SpookyET>
see all that green on the right?
15:25
<Lachy>
SpookyET, what's your point? we know that already
15:28
<SpookyET>
Lachy: I was talking to hsivonen
15:28
<Lachy>
I realise that, but he knows too
15:29
<SpookyET>
Let him speak for himself.
15:31
<Lachy>
I'm trying to determine what your point is by telling people things we already know?
15:32
<zcorpan>
hsivonen: yeah, that's something to blog about :)
15:40
<Dashiva>
At the moment it looks like a lot of colorblind scandinavian flags in Opera
15:40
<hsivonen>
SpookyET: I don't understand what point you are trying to make to me
15:40
<SpookyET>
No point. I was stating a fact.
15:41
<hsivonen>
ok
15:41
<Lachy>
you can get it to work in Firefox 3 if you just change document.addEventListener to window.addEventListener. (that is, until Hixie adds more tests to it later)
15:43
<hsivonen>
gotta respect the people who send patches for Lynx. last time I looked the source wasn't pretty
15:46
<Dashiva>
Acid3 uses HTML 4.0 doctype... am I missing something, or was it a random choice?
15:47
<zcorpan>
Dashiva: Hixie probably copied it from damowmow.com or something
15:47
<hsivonen>
that's what happened with Acid2, IIRC
15:48
<zcorpan>
or wait, damowmow uses 4.01
15:48
<zcorpan>
then hixie.ch or something :)
15:50
<hsivonen>
the comment in the damowmow source is funny
15:50
<zcorpan>
heh
15:51
<SpookyET>
Adobe's Apollo is pretty interesting. I just stumbled upon it. It seems to be a competitor to Microsofts XAML.
15:52
<hsivonen>
I don't understand the Adobe-internal politics that produced Apollo considering that they have Flash
15:52
<SpookyET>
It uses Flash, Acrobat, HTML, CSS, JavaScript.
15:52
<zcorpan>
the new Ajax?
15:53
<SpookyET>
The cool thing about Apollo is that it uses WebKit, while Microsoft's solution uses IE's rendering engine.
15:53
<SpookyET>
http://www.niallkennedy.com/blog/archives/2007/03/adobe-apollo.html
15:53
<SpookyET>
zcorpan: It's not AJAX. It's designed to merge desktop and web apps.
15:54
<Lachy>
it's like their own version of Widgets
15:54
<SpookyET>
It's not widgets, but full apps.
15:54
<zcorpan>
SpookyET: ok
15:55
<SpookyET>
https://ssl.blogs.zdnet.com/blogs/Stewart/images/apollo_mac_library_large.png
15:56
<SpookyET>
It looks like you create a hybrid desktop + web app instead of a desktop client that connects to a web service.
15:56
<Lachy>
Interesting. I just found out that for DOCTYPE sniffing, IE ignores the language code at the end of <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">, whereas in FF it needs to be EN or it triggers standards mode
15:57
<hsivonen>
Lachy: interesting indeed. I wonder why the IE team chose to look inside the identifier
15:57
<Dashiva>
They're big on localization? :)
15:57
<hsivonen>
Lachy: Gecko lowercases the string and compares it against a list of strings
15:57
<Lachy>
probably because there are silly people around who change the "EN" to their own native langauge
15:58
<Lachy>
it makes sense to do what IE does
15:58
<hsivonen>
Lachy: yeah, but shouldn't those silly people get the quirks mode
15:58
<Lachy>
yes, they do in IE. They don't in FF, that's my point
15:58
<hsivonen>
Lachy: considering that sniffing is a heuristic for deciding if the author had clue
16:00
<Philip`>
I'd like a "-//W3C//DTD HTML 4.01 Transitional//EN-GB" with <centre> and <font colour="grey">
16:00
<Lachy>
and in IE, the number needs to be 2, 3 or 4 to trigger quirks mode (decimal points ignored)
16:01
<zcorpan>
ie's doctype sniffing is insane. the way the system id also matters iirc
16:01
<zcorpan>
er, the say the system id is written...
16:01
zcorpan
-> food
16:02
<Lachy>
Philip`, the langauge code is basically irrelevant even in SGML. It's supposed to refer to the language that the DTD is written in, but I have no idea why that's relevant at all
16:06
<Philip`>
(Incidentally, I was actually surprised when seeing that CSS3 Color supports "grey" and that it actually works in browsers - I'm certain it used to be interpreted as "green" in the past (like, uh, Netscape 3 or something))
16:07
<Lachy>
wow
16:07
<Dashiva>
I remember some early Opera canvas bug which interpreted random strings as colors. E.g. "bogus" became pink, if I recall correctly
16:08
<Philip`>
I just want to know how anybody is ever going to implement the "flavor" colour
16:08
<hasather>
"crap" became brown in IE before, I think. Dunno if that still works
16:09
<Lachy>
hasather, yep, still works!
16:09
<Lachy>
bogus becomes ping in IE too!
16:10
<Dashiva>
I suspect it has to do with trying to interpret it as hex, but the details elude me
16:11
<Lachy>
it seems that it throws away any letters other than [A-Fa-f]
16:13
<Lachy>
then replaces them with 0, so "bogus" becomes "b00000"
16:13
<Lachy>
and "crap" becomes "c0a000"
16:14
<Lachy>
I wonder if that's specced in HTML5...
16:14
<Philip`>
It work for "bogo" but not "bog" - it seems to only do that for >= 4 characters
16:14
<Lachy>
for the various color attributes
16:15
<Dashiva>
If there's a site relying on that, I will personally hunt down the author
16:15
<Philip`>
At least in FF3, it's quirks-only
16:15
<SpookyET>
Maybe, it should support non-us spelling:-)
16:15
<Dashiva>
What does 'beos' give you, Lachy?
16:15
<SpookyET>
background-colour
16:16
<Lachy>
Dashiva, "beos" gives "be0000"
16:16
<Philip`>
Maybe the browser developers were trying to be nice to authors who misread books with bad fonts, and tried writing <body bgcolor="ffooff">?
16:16
<Lachy>
SpookyET, doesn't work for CSS, only for the HTML attributes
16:16
<Dashiva>
Lachy: Hmm, in the bug I mentioned it became green
16:17
<Philip`>
(Quirks-only in Opera 9 too)
16:17
<Lachy>
Dashiva, which bug?
16:17
<Lachy>
and which browser?
16:19
<Dashiva>
Opera in the first stages of canvas support
16:19
<Dashiva>
Just after the "blue is red on windows" bug :)
16:19
<Philip`>
(Oh, it's doing bo=#b00000, bog=#0b0000, bogo=#b00000, and cra=#0c0a00 - I can see why it's called "quirks"...)
16:20
<Lachy>
Philip`, which browser are you getting those results?
16:20
<Lachy>
there shouldn't be a leading 0 on the values for bog and cra
16:20
<Philip`>
Oh, that was Opera 9
16:21
<Philip`>
but FF3 doesn't do that
16:21
<Philip`>
(Yay, non-interoperability)
16:22
<Philip`>
(FF3 just gives #000000 for anything <= 3 characters, it seems)
16:22
<Dashiva>
Time to run a bruteforce scan of all possible combinations on 1-6 letters, then!
16:23
<Lachy>
Dashiva, you only need to do 3 to 6, and letters A-F and one other
16:24
<Lachy>
e.g. bgcolor="azz", "bzz", ...
16:24
<Philip`>
Lachy: Not quite that simple - Opera ignores up to one leading #, and any spaces
16:26
<Philip`>
In Opera, "f f f f f" == #fffff0; in FF, it's #f00ff0 (?!)
16:26
<Lachy>
oh, 1 and 2 letters give weird results too
16:28
<Lachy>
Safari does it in standards mode
16:30
<Philip`>
With <body bgcolor=" f f f "> I get grey in FF, almost-black in Opera, and green in Konqueror
16:33
<Philip`>
zcorpan: You said you wanted to spec quirks mode? ;-)
16:33
<Lachy>
nice, <body bgcolor="rainbow"> give a diff colour in nearly every browser :-)
16:35
<Philip`>
http://lxr.mozilla.org/mozilla/source/gfx/src/nsColor.cpp#126
16:35
<Philip`>
so it always does black for <= 3 chars (excluding the optional leading #)
16:35
<Lachy>
someone want to check webkit source, it seems to be closer to IE
17:40
<zcorpan>
Philip`: yes, test cases welcome
17:45
<SpookyET>
I keep getting disconnected.
17:47
<SpookyET>
Has anyone seen Flashtml? :-) www.pierinc.com Thank you for killing my scrollbar and back button. But, for a second, it fools you into thinking that it's html and dhtml animations.
17:50
zcorpan
will use http://del.icio.us/zcorpan/quirks to pile up quirks
19:28
<zcorpan>
yay! ftp works again. i have *no* idea why it didn't work before
19:36
zcorpan
considers moving valid-html5.png out of temp/
19:43
<zcorpan>
done
20:24
<zcorpan>
started to draft on my presentation http://simon.html5.org/temp/html5-geekmeet.html
20:24
<zcorpan>
(in swedish)
20:26
<Philip`>
"Cross-document messanging" - spurious n?
20:26
<zcorpan>
oops
20:27
<zcorpan>
fixed
20:33
hsivonen
learns that boilerplate is boilerplate in Swedish :-)
20:34
<zcorpan>
probably isn't
20:34
<zcorpan>
don't know a good swedish word for it :)
20:34
<hsivonen>
zcorpan: looks good
20:35
<zcorpan>
thanks. have two canvas demos iframed, commented out for now
20:43
<Philip`>
Be careful that the second doesn't suck up all your CPU while you're trying to get on with the rest of the presentation :-)
20:44
<zcorpan>
yeah, fortunately it can be paused :)
20:44
<zcorpan>
not sure i'll use those at all though
20:45
<zcorpan>
but having a "3d" fps game in 2d canvas is cool, so i want to include it
20:46
<Philip`>
Oh, can it?
20:46
<Philip`>
Aha, the "pause" key - that makes sense
20:46
<zcorpan>
there's also a pause button
20:47
<Philip`>
Oh, okay, on the 84 version since I didn't remove the debug bit at the bottom
20:49
<Philip`>
(The 2d canvas is quite nasty for doing this 3d stuff in, though :-p )
20:50
<Philip`>
(It's nice that you can do it, but it isn't really playing to the strengths of the canvas)
20:51
<zcorpan>
indeed. it's like using GIF for video
20:51
<Philip`>
((It is quite fun, though))
20:53
<Philip`>
Perhaps it's more like using ASCII art over Telnet for video
20:54
<zcorpan>
heh, ok
20:56
<Philip`>
(That reminds me, I did a (rubbish) text-based multiplayer deathmatch FPS game over the IRC protocol (though not a real IRC server) once - it would be nice to integrate that with the canvas code and get browser-based multiplayer deathmatch...)
21:35
<Philip`>
(Hixie: I think the spec has a spare > in Scripting/Origin with "<span>browsing context</span>>")