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

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

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

           Summary: FIGCAPTION should be allowed to NOT be exactly
                    first/last child of FIGURE ("The figcaption element"
                    spec section)
           Product: HTML WG
           Version: unspecified
          Platform: PC
               URL: http://www.w3.org/TR/html5/grouping-content.html#the-f
                    igcaption-element
        OS/Version: Windows XP
            Status: NEW
          Severity: critical
          Priority: P2
         Component: HTML5 spec (editor: Ian Hickson)
        AssignedTo: ian@hixie.ch
        ReportedBy: mtanalin@yandex.ru
         QAContact: public-html-bugzilla@w3.org
                CC: mike@w3.org, public-html-wg-issue-tracking@w3.org,
                    public-html@w3.org


Section: "The figcaption element"
(http://www.w3.org/TR/html5/grouping-content.html#the-figcaption-element)

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

This is bad and harmful requirement. FIGCAPTION should be allowed to be placed
inside DIV (_common_ container element) (or inside one of _any_ number of
nested DIVs) as well as after/before any other element inside FIGURE element.
"First/last child" requirement makes many visual designs unimplementable. For
example, DIV-wrapping might be needed to place something to the left of figure
caption with arbitrary paddings and so on.

Otherwise, FIGCAPTION will be just dropped by web developers when, according to
specific visual design, FIGCAPTION just cannot be exactly first or last child
of FIGURE element.

Spec should not force web developers to use wrong semantic solutions. Using any
element different from FIGCAPTION (where actually FIGCAPTION is semantically
appropriate) in place of FIGCAPTION (or dropping validation and semantic
correctness itself at all) just because "validator said this is invalid" is
wrong.

Thanks.

-- 
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 19:02:54 UTC

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