Comments on: Hello, summary and figcaption elements

By: [分享]The details and summary elements « NeverBest!我还能做的更好 – 007boy | im007boy

Sun, 14 Aug 2011 09:08:33 +0000

[...] Hello, summary and figcaption elements [...]

By: Bruce Lawson

Bruce Lawson — Tue, 03 Aug 2010 17:26:05 +0000

Anon- it depends on the implementation. Nothing like this is required or forbidden by the specification.

By: anon

anon — Tue, 03 Aug 2010 17:08:46 +0000

Will the implementation include an automatic scroll down when the content is not visible in the viewport (only if the summary+details max height < viewport height)?

By: Adam Boarman's dot com » Blog Archive » The figure & figcaption elements

Thu, 24 Jun 2010 08:14:13 +0000

[...] readers will know that a new element was recently introduced, namely

. Who knows if it’ll stick, but for now here’s what the spec [...]

By: New HTML5 elements: summary & figcaption - Gurushala

New HTML5 elements: summary & figcaption - Gurushala — Sun, 28 Feb 2010 00:29:33 +0000

[...] two new HTML elements: summary and figcaption were added to HTML5 project. The creation of these new elements to the [...]

By: Alohci

Alohci — Thu, 25 Feb 2010 00:43:32 +0000

@fjpoblam – The figcaption needs to be a direct child of figure. You can put the tags outside the

tags to achieve what you’re trying to do in a valid way.

By: fjpoblam

fjpoblam — Wed, 24 Feb 2010 16:12:38 +0000

Probably, I misunderstand the intent of

and should be using

instead, as I see the W3 validator rejects what I’m trying:

[text]

The W3 validator wants an for the and a separate inside the

By: bractus

bractus — Thu, 18 Feb 2010 17:33:35 +0000

Hi Bruce

Do you have any document shows logic order of html5 tags? I mean shows what is the best practice using tags within each other.
For example, I saw a developer is using

By: Bruce Lawson

Bruce Lawson — Mon, 08 Feb 2010 09:34:06 +0000

JoshS

my reading is same as yours. But I think that they way details is currently specified is enough for the 80% of authorial needs.

By: JoshS

JoshS — Fri, 05 Feb 2010 20:44:07 +0000

If I read the spec correctly, the summary tag is always visible, and everything else in the details tag is only visible when the open attribute is set. Pillar Magazine Example

Assuming this is correct, I have some comments about the summary tag. The content model for the summary tag is phrasing content, which means it can only contain other phrasing content.

What if you want to have more complex info in the summary. As an example, I’m thinking about the Facebook Settings page. They have a setting heading, description and current value. When you show the “details” area, you see the edit fields (like the Pillar Magazine example, BUT some of the “summary” is not visible.

I can’t see this working with summary as currently defined unless, summary is not phrasing content or if other child elements of the details element could be visible when it is “closed.”