[Bug 12835] FIGCAPTION should be allowed to NOT be exactly first/last child of FIGURE ("The figcaption element" spec section)

http://www.w3.org/Bugs/Public/show_bug.cgi?id=12835

--- Comment #5 from Marat Tanalin <mtanalin@yandex.ru> 2011-06-03 15:18:21 UTC ---
(In reply to comment #4)
> If you're just inserting <div>s for
> styling, they don't carry any semantics whatsoever.  It doesn't matter whether
> they're inside or outside the <figcaption>.

The bug is not about just wrapping FIGCAPTION in DIVs (it would be pointless).
It's not about styling legend at all.

The bug is about _ordering_ elements: it should be possible to place sibling
elements before and after FIGCAPTION to make possible implementing arbitrary
designs. Such sibling elements may contain text or functional elements (not
just some empty divs). To make this possible, LEGEND should be allowed to be
wrapped in DIVs. Such DIVs would contain FIGCAPTION _and_ sibling elements
that, according to site design, should be in place that is not allowed by
current HTML5 spec.

Currently, FIGCAPTION element is similar to attribute and therefore mostly
useless. It does exist, but can't be styled and placed where it needs to be
according to arbitrary visual design.

If semantic element (FIGCAPTION) does NOT allow to implement specific site
design while other elements (e.g., headers, divs) DO, the element will be just
ignored in practice in favor to less semantic alternatives that allow to
perform a real task.

Does semantic elements exist to be ignored in practice due to purely
theoretical, nonsensical and wrong spec limitation? Unlikely.

HTML5 spec should be free from such artificial and pointless limitations.

Same applies to LEGEND element (bug 12834).

-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.

Received on Friday, 3 June 2011 15:18:23 UTC