00:07
<jcranmer>
wow, that quit message tripped me up
00:07
<jcranmer>
one of my friend's names is burton
00:16
<Hixie>
does he work at lockheed martin?
00:17
<jcranmer>
still at university
00:17
<Hixie>
bummer
00:17
<Hixie>
wouldn't it have been awesome if i had been right though
00:18
<alyoshka>
is it <details open="true"> or <details open="open">?
00:19
<alyoshka>
and does <details open="false"> or <details open="closed"> work?
00:20
<alyoshka>
attribute minimization isn't allowed in XHTML, and HTML5 is aiming for an XHTML implementation, so this is important
00:20
<Hixie>
it's <details open=""> and <details>
00:21
<Hixie>
(<details open="open"> is also allowed. the actual value has no effect, only the presence or absence of the attribute matters.)
00:22
<alyoshka>
thanks. and would the javascript interface include setAttribute("open", "anythinggoeshere")?
00:22
<Hixie>
anything will work, but only "" and "open" are allowed for the second argument (they both open the element)
00:22
<Hixie>
see http://www.whatwg.org/specs/web-apps/current-work/#the-details-element
00:22
<Hixie>
in particular, notice it says that "The open content attribute is a boolean attribute."
00:23
<Hixie>
and then see http://www.whatwg.org/specs/web-apps/current-work/#boolean-attribute
00:23
<alyoshka>
ah, I see, that "boolean attribute" part confused me at first
00:23
<Hixie>
once browsers implement <details>, there'll also be a .open DOM attribute
00:23
<Hixie>
the section, or the term?
00:23
<alyoshka>
the term
00:23
<Hixie>
ah
00:23
<alyoshka>
I missed the explaination
00:23
<Hixie>
always follow hyperlinks to read the definitions :-)
00:24
<Hixie>
the terms in html5 are not always what they appear (usually due to a lack of more appropriate terms)
00:24
<alyoshka>
that page always make Opera run so slow while loading so sometimes I'm too lazy to open it
00:25
<alyoshka>
lol, I know , it's bad
00:25
<alyoshka>
is there a sectioned version of the spec?
00:26
<xydyx>
http://www.whatwg.org/specs/web-apps/current-work/multipage/
00:26
<Hixie>
http://whatwg.org/html5
00:26
<Hixie>
^ multipage version
00:26
<Hixie>
it says so right at the top of the document :-)
00:27
<alyoshka>
thanks
00:30
<alyoshka>
coolness, I made a simple style rule that takes care of open/closed
00:31
<alyoshka>
it excludes IE6 and 7 tho AFAIK
00:31
<alyoshka>
uses the :before pseudo-element
00:35
<alyoshka>
say, should the contents of <details> (except for the triangle) be a bit indented?
00:36
<alyoshka>
> Details
00:36
<alyoshka>
\/ Details
00:36
<alyoshka>
The details
00:37
<alyoshka>
\/ Details
00:37
<alyoshka>
--The details
00:37
<alyoshka>
something like that?
00:37
<alyoshka>
where the content lines up with the legend text, past the triangle
00:38
<alyoshka>
well, it's probably going to be the choice of the UA developers, but I mean, like a recommended style
00:44
<alyoshka>
yikes, Firefox thinks the whole page down from the <legend> is wrapped in a <fieldset> since there's a <legend> there
00:46
<Hixie>
alyoshka: http://www.whatwg.org/specs/web-apps/current-work/multipage/rendering.html#the-details-element-0
18:49
<annevk5>
it sort of seems rendering should be normative for Web browsers at least given that we're effectively required to implement that anyway
18:52
<Philip`>
There will be some class of web browsers that need to do things differently (e.g. because they're on constrained devices)
18:53
<Philip`>
and it seems unreasonable to try to precisely define what class of UAs the requirements are required for
18:53
<Philip`>
so it'd end up being effectively optional, because any browser developer could claim they're not in the class that the normative rendering requirements apply to
18:53
<Philip`>
and so they might as well be non-normative