9535 2010-04-16 07:39:16 +0000 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. 2010-10-04 13:54:23 +0000 1 1 1 Unclassified HTML WG pre-LC1 HTML5 spec (editor: Ian Hickson) unspecified Other other RESOLVED FIXED http://www.whatwg.org/specs/web-apps/current-work/#the-figure-element P3 normal LC 1 contributor ian hsivonen ian mike public-html-admin public-html-wg-issue-tracking zcorpan public-html-bugzilla oldest_to_newest 35092 0 contributor 2010-04-16 07:39:16 +0000 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 35124 1 ian 2010-04-18 01:52:57 +0000 Henri, as one of the people who's had the most experience with the new parser rules, do you have any feedback on this? 35157 2 hsivonen 2010-04-20 13:25:25 +0000 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. 36875 3 ian 2010-07-14 22:01:05 +0000 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. 36876 4 contributor 2010-07-14 22:02:40 +0000 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