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 6440 - To which elements applies the formatBlock command?
Summary: To which elements applies the formatBlock command?
Status: VERIFIED FIXED
Alias: None
Product: HTML WG
Classification: Unclassified
Component: pre-LC1 HTML5 spec (editor: Ian Hickson) (show other bugs)
Version: unspecified
Hardware: All All
: P4 normal
Target Milestone: ---
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
URL:
Whiteboard:
Keywords: NoReply
Depends on:
Blocks:
 
Reported: 2009-01-15 12:45 UTC by Anne
Modified: 2010-10-04 14:47 UTC (History)
4 users (show)

See Also:

Attachments

Description Anne 2009-01-15 12:45:30 UTC 
In http://www.whatwg.org/specs/web-apps/current-work/multipage/editing.html#command-formatblock "prose element" and "phrasing element" need to be changed because they are no longer hyperlinks. Currently it is hard to figure out to which elements this command applies.
Comment 1 Simon Pieters 2009-01-15 13:14:30 UTC 
Assuming 'flow content' and 'phrasing content' are intended, it's wrong.

Before it was a fixed list:

<address> 
<aside> 
<h1> 
<h2> 
<h3> 
<h4> 
<h5> 
<h6> 
<nav> 
<p> 
<pre>

(Although at least Opera supports <div> too.)

Now we have these additions, some of which are questionable at best:

<section>
<article>
<header>
<footer>
<hr>
<dialog>
<blockquote>
<ol>
<ul>
<dl>
<a>?
<ins>?
<del>?
<figure>
<map>
<table>
<form>
<fieldset>
<details>
<datagrid>
<menu>

I'd suggest going back to a fixed list.
Comment 2 Ian 'Hixie' Hickson 2009-05-25 01:27:04 UTC 
I came up with some sort of solution. Not sure I like it.
Comment 3 Maciej Stachowiak 2010-03-14 13:16:20 UTC 
This bug predates the HTML Working Group Decision Policy.

If you are satisfied with the resolution of this bug, 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

This bug is now being moved to VERIFIED. Please respond within two weeks. If this bug is not closed, reopened or escalated within two weeks, it may be marked as NoReply and will no longer be considered a pending comment.