This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 9535 - Consider the poem example of figure. It should be possible to omit the </p> tag there. Maybe we should make <figcaption> imply </p> in the parser.
Summary: Consider the poem example of figure. It should be possible to omit the </p> t...
Status: RESOLVED FIXED
Alias: None
Product: HTML WG
Classification: Unclassified
Component: pre-LC1 HTML5 spec (editor: Ian Hickson) (show other bugs)
Version: unspecified
Hardware: Other other
: P3 normal
Target Milestone: LC
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
URL: http://www.whatwg.org/specs/web-apps/...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-04-16 07:39 UTC by contributor
Modified: 2010-10-04 13:54 UTC (History)
6 users (show)

See Also:

Attachments

Description contributor 2010-04-16 07:39:16 UTC 
Section: http://www.whatwg.org/specs/web-apps/current-work/#the-figure-element

Comment:
Consider_the_poem_example_of_figure._It_should_be_possible_to_omit_the_</p>_ta
g_there._Maybe_we_should_make_<figcaption>_imply_</p>_in_the_parser.

Posted from: 85.227.159.51 by simonp@opera.com
Comment 1 Ian 'Hixie' Hickson 2010-04-18 01:52:57 UTC 
Henri, as one of the people who's had the most experience with the new parser rules, do you have any feedback on this?
Comment 2 Henri Sivonen 2010-04-20 13:25:25 UTC 
Making <figcaption> imply </p> isn't probably any worse than making <article>, <footer>, etc. imply </p>.

However, making any new elements imply </p> is really questionable considering our supposed backwards and forwards-compatibility stories.
Comment 3 Ian 'Hixie' Hickson 2010-07-14 22:01:05 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:
   http://dev.w3.org/html5/decision-policy/decision-policy.html

Status: Accepted
Change Description: see diff given below
Rationale: Concurred with reporter's comments.

This actually turns out to have been an oversight — I had meant all elements that take "flow content" as their content model to do this, but I forgot when adding figcaption and summary.
Comment 4 contributor 2010-07-14 22:02:40 UTC 
Checked in as WHATWG revision r5166.
Check-in comment: Make <figcaption> and <summary> act like other elements that have 'flow content' content models.
http://html5.org/tools/web-apps-tracker?from=5165&to=5166