W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > December 2011

[Bug 12834] LEGEND should be allowed to NOT be exactly first child of FIELDSET ("The legend element" spec section)

From: <bugzilla@jessica.w3.org>
Date: Sun, 04 Dec 2011 18:01:52 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1RXGNs-0003VU-22@jessica.w3.org>

--- Comment #19 from Benjamin Hawkes-Lewis <bhawkeslewis@googlemail.com> 2011-12-04 18:01:51 UTC ---
(In reply to comment #18)
> (In reply to comment #17)
> The testcases just bulletproofly illustrate how _layout_ possibilities can be
> heavily limited by purely theoretical spec-requirement contradicting to actual
> browser support.

Indeed, and as such they do not answer my question.

It's not obvious to me that the only way to achieve the layout effects you
mention is to put the extra text inside fieldset, but more generally if you
cannot determine the semantics you need to express, then you cannot determine
the actual DOM that needs styling, so you cannot begin to assess whether CSS
does or does not include the features required to achieve the layouts you want.

> If some effect is needed for layout, then it will be achieved _anyway_. And if
> it cannot be achieved using semantic LEGEND element just because 'spec says
> this is invalid', then just an other element will be used instead of LEGEND.

Perhaps. But this might imply a deficiency to be fixed in CSS not HTML. 

> By the way, this rationale is quite clearly described in description (comment 0) of the bug.

I read Comment 0, but it doesn't describe the semantic relationships in play.

Perhaps pointing to some real-world designs would help clarify what semantics
these odd layouts are attempting to visually express?

Configure bugmail: https://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 Sunday, 4 December 2011 18:01:57 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:02:09 UTC