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

[Bug 12834] New: Section: "The legend element" (http://www.w3.org/TR/html5/forms.html#the-legend-element). Wrong spec part: "Contexts in which this element can be used: As the first child of a fieldset element." This is bad and harmful requirement. LEGEND should be allowe

From: <bugzilla@jessica.w3.org>
Date: Tue, 31 May 2011 18:30:32 +0000
To: public-html@w3.org
Message-ID: <bug-12834-2495@http.www.w3.org/Bugs/Public/>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=12834

           Summary: Section: "The legend element"
                    (http://www.w3.org/TR/html5/forms.html#the-legend-elem
                    ent). Wrong spec part: "Contexts in which this element
                    can be used: As the first child of a fieldset
                    element." This is bad and harmful requirement. LEGEND
                    should be allowe
           Product: HTML WG
           Version: unspecified
          Platform: Other
               URL: http://www.whatwg.org/specs/web-apps/current-work/#top
        OS/Version: other
            Status: NEW
          Severity: normal
          Priority: P3
         Component: HTML5 spec (editor: Ian Hickson)
        AssignedTo: ian@hixie.ch
        ReportedBy: contributor@whatwg.org
         QAContact: public-html-bugzilla@w3.org
                CC: mike@w3.org, public-html-wg-issue-tracking@w3.org,
                    public-html@w3.org


Specification: 
Section: http://www.whatwg.org/specs/web-apps/current-work/#top

Comment:
Section: "The legend element"
(http://www.w3.org/TR/html5/forms.html#the-legend-element).

Wrong spec part: "Contexts in which this element can be used: As the first
child of a fieldset element."

This is bad and harmful requirement. LEGEND should be allowed to be placed
inside DIV (_common_ container element) as well as after any other element.
"First child" requirement makes many visual designs unimplementable. For
example, DIV-wrapping might be needed to place something to the left of legend
with arbitrary paddings and so on.

Currently, web developers are forced to just _drop_ LEGEND element in such
cases and just use another element (e.g. H2-H6 element) instead of LEGEND when
exactly LEGEND would be more appropriate than H2, but is not allowed just
because "validator said this is invalid".

Spec should not force web developers to use wrong semantic solutions. Using H2
(or any other element) in place of LEGEND (where actually LEGEND is
semantically appropriate) is wrong.

Probable correct description for contexts in which LEGEND can be used:
"First _structural_ (semantic) parent element of LEGEND should be FIELDSET".
This means that FIELSET can contain any number of nested DIV elements, and
LEGEND may be inside one of them as well as (but NOT only allowed) direct
child of FIELDSET, and order of elements (including LEGEND) inside FIELDSET
can be _any_ that is necessary in a specific case (LEGEND should NOT be needed
to be exactly first semantic child of FIELDSET).

Otherwise, LEGEND will be just dropped by web developer in cases when LEGEND
just cannot be exactly first child according to specific visual design layout.


Thanks.

Posted from: 217.172.29.1
User agent: Mozilla/5.0 (Windows NT 5.1; rv:2.0.1) Gecko/20100101 Firefox/4.0.1

-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
Received on Tuesday, 31 May 2011 18:30:34 UTC

This archive was generated by hypermail 2.3.1 : Monday, 29 September 2014 09:39:25 UTC