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

[Bug 11598] Figure element should not be restricted to flow agnostic images/videos/etc. "The element can thus be used to annotate illustrations, diagrams, photos, code listings, etc, that are referred to from the main content of the document, but that could, without

From: <bugzilla@jessica.w3.org>
Date: Tue, 11 Jan 2011 20:09:56 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1PckXU-0008NU-Sf@jessica.w3.org>

Ian 'Hixie' Hickson <ian@hixie.ch> changed:

           What    |Removed                     |Added
             Status|NEW                         |RESOLVED
                 CC|                            |ian@hixie.ch
         Resolution|                            |WONTFIX
            Summary|Figure element should not   |Figure element should not
                   |be restricted to flow       |be restricted to flow
                   |agnostic images/videos/etc. |agnostic images/videos/etc.
                   |"The element can thus be    |"The element can thus be
                   |used to annotate            |used to annotate
                   |illustrations, diagrams,    |illustrations, diagrams,
                   |photos, code listings, etc, |photos, code listings, etc,
                   |that are referred to from   |that are referred to from
                   |the main content of the     |the main content of the
                   |document, but that could    |document, but that could,
                   |                            |without
            Summary|without                     |

--- Comment #1 from Ian 'Hixie' Hickson <ian@hixie.ch> 2011-01-11 20:09:56 UTC ---
EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are
satisfied with this response, please change the state of this bug to CLOSED. If
you have additional information and would like the editor to reconsider, please
reopen this bug. If you would like to escalate the issue to the full HTML
Working Group, please add the TrackerRequest keyword to this bug, and suggest
title and text for the tracker issue; or you may create a tracker issue
yourself, if you are able to do so. For more details, see this document:

Status: Rejected
Change Description: no spec change
Rationale: It's not invalid. The spec doesn't say that <figure> must not be
used for inline figure, it just says that <figure> can be used for things that
could be taken out of flow. The only normative text is "The figure element
represents some flow content, optionally with a caption, that is self-contained
and is typically referenced as a single unit from the main flow of the
document." (it's normative due to the definition of the word "represents"), and
that sentence is consistent with the usage above.

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 Tuesday, 11 January 2011 20:09:58 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 16:31:03 UTC