08:48
<hsivonen>
Hixie: I'm getting personal feedback that disapproves of giving semantics to previously presentational elements like <small>. Do you have a PR story I could refer to?
11:12
<jgraham>
In pre/textarea blocks only the first newline gets dropped, right?
11:13
jgraham
has discovered that some html5lib testcases drop more which seems like a bug
11:13
<jgraham>
or, I suppose I'm making a mistake...
11:21
<hsivonen>
Hixie: have you run a Google analysis on what percentage (permilliage?) of text/html pages have an <svg> or <math> tag in them?
11:21
<hsivonen>
Hixie: that is, would we break the Web if we fixed MathML in HTML and SVG in HTML?
12:40
<Jero>
sweet: http://digg.com/programming/HTML5_differences_from_HTML4
12:41
<Jero>
hopefully showing this document to a large audience as digg will make people understand html5 better
13:53
<Dashiva>
Jero: From the comments there, it seems many people don't want to understand :)
14:00
<krijnh>
'I will never leave you center tag, my love :('
14:00
<krijnh>
Hehe
14:01
<Jero>
yeah, some comments are pretty humorous :p
14:01
<krijnh>
They aren't too bad
14:03
<Jero>
Dashiva: I suppose you're right but at least we make them think about it
14:04
<Jero>
and some critique is actually IMO not completely wrong
14:05
<annevk>
anything new?
14:05
<annevk>
besides the digg link above :)
14:05
Philip`
guesses that getting random patterns of colours (presumably picking up random sections of memory) in canvas drawing is not entirely optimal from a security point of view
14:05
<annevk>
guess the debate on XHTML is settled with that...
14:05
<annevk>
XHTML5*
14:06
<krijnh>
"XHTML is the future. I can't wait for XHTML2." - that's too bad then
14:06
<Jero>
i see a lot of people that are confused with the naming
14:07
<Jero>
"What is the XHTML 5.0? I've heard about HTML 5.0 and XHTML 2.0. Did the naming is changed?"
14:07
<annevk>
heh, they're promoting my blog
14:07
<krijnh>
Did Digg users undergo an upgrade or something?
14:08
<annevk>
yeah, the last time they looked at HTML5 it kind of sucked, now it rules
14:08
<krijnh>
Indeed
14:08
<Jero>
i think it got popular because Kevin Rose was one of the first to digg it
14:09
<Jero>
and many people have him as a friend, so that way it becomes instantly popular
14:09
<krijnh>
Yay for web2.0
14:10
<Jero>
"HTML 5...wouldn't that mean that Web 5.0 isn't far off?" wtf...
14:10
<annevk>
"HTML5 is so strict that it steps on my balls while wearing high heels"
14:11
<krijnh>
"He didn't say he didn't enjoy it."
14:11
<annevk>
Jero, we've been talking about Web 5.0 a lot here, actually
14:11
<Jero>
oh snap, i've been missing out
14:11
<krijnh>
XML5, HTTP5, WEB5, where does it end :)
14:11
<krijnh>
CSS5
14:11
<krijnh>
DOM5
14:12
<krijnh>
R5
14:12
<annevk>
SVG5
14:12
<Philip`>
Implemented in Firefox 5 and Safari 5? And, uh, Opera 15?
14:12
<krijnh>
Opera5 prolly already supported all of this anyway
14:12
<annevk>
Opera 2^5
14:13
<Philip`>
Opera X.5, maybe
14:14
<annevk>
I like to think I'm better informed :p
14:14
<krijnh>
Yeah, you have that habit ;)
14:47
<annevk>
jgraham, would be good if you could e-mail that yes
14:48
<annevk>
jgraham, either to the list or just to me
14:48
<jgraham>
annevk: You are referring to the HTML4/5 differences thing?
14:49
<annevk>
yeah
14:50
<annevk>
http://penguinpetes.com/b2evo/index.php?title=here_comes_html5_duck&more=1&c=1&tb=1&pb=1
14:51
<Dashiva>
It's sort of depressing to see people ask "Why add <header>, <aside>, <section>, etc when we have <div> already?"
14:51
<Dashiva>
And these are the people who claim they want semantic markup?
14:53
<annevk>
jgraham, I like your suggestions btw, I'll guess I'll look into them tomorrow or Monday or so
14:54
<annevk>
wow, there's lots of people who linked to that story overnight
14:54
<jgraham>
Dashiva: One of the suggestions I'm going to add to my list for Anne is to mention that nesting <section> alters heading depth like <h1>-<h6>
14:55
<annevk>
Yeah, we should probably group some of the new elements together that take part in a model
14:55
<annevk>
maybe also have a table at the end that has all the differences as a simple overview including links to the spec or something
14:58
<hsivonen>
are there cases when "insertion point" is not either undefined or just before the next input character?
14:59
annevk
isn't sure
15:00
<hsivonen>
annevk: does html5lib support document.write()?
15:00
<annevk>
in theory
15:01
<annevk>
we have a stream that you can inject into
15:01
<hsivonen>
ok. I wonder if I should implement tokenizer-level support for document.write()
15:01
<hsivonen>
if I do, it'll be asynchronous
15:02
<hsivonen>
so that the method will return immediately and the caller may listen to an event indicating when the buffer has been parsed
15:02
<hsivonen>
I'm not sure whether all this is worth the trouble, though
15:03
<annevk>
prolly not
15:07
<hsivonen>
it would be reasonably easy to push the current input buffer state on a stack if the insertion point is never weirder than "before the next input character"
17:53
<Jero>
I assume this is in the close tag open state? http://html5.org/tools/web-apps-tracker?from=900&to=901