On Fri, 09 Sep 2011 00:09:39 +0200, Ian Hickson <i...@hixie.ch> wrote:
On Fri, 6 May 2011, Simon Pieters wrote:
> Modified: source
> ===================================================================
> --- source 2011-05-05 22:03:52 UTC (rev 6087)
> +++ source 2011-05-05 22:45:13 UTC (rev 6088)
> @@ -105238,7 +105238,6 @@
> <dd><p>Use an explicit <code>form</code> and <span
> title="attr-input-type-text">text field</span> combination
instead.</p></dd>
> <dt><dfn><code>listing</code></dfn></dt>
> - <dt><dfn><code>xmp</code></dfn></dt>
> <dd><p>Use <code>pre</code> and <code>code</code> instead.</p></dd>
> <dt><dfn><code>nextid</code></dfn></dt>
> @@ -105256,6 +105255,9 @@
> <dt><dfn><code>strike</code></dfn></dt>
> <dd><p>Use <code>del</code> instead if the element is marking an
edit,
> otherwise use <code>s</code> instead.</p></dd>
> + <dt><dfn><code>xmp</code></dfn></dt>
> + <dd><p>Use <code>code</code> instead, and escape "<code
> title=""><</code>" and "<code title="">&</code>" characters as
"<code
> title="">&lt;</code>" and "<code title="">&amp;</code>"
> respectively.</p></dd>
For xmp it should say "Use pre and code ..." since just code is not a
drop-in
replacement for xmp.
Good point.
I went with "pre or code". I don't think you'd use both, typically,
right?
"To represent a block of computer code, the pre element can be used with a
code element"
http://www.whatwg.org/specs/web-apps/current-work/complete/grouping-content.html#the-pre-element
Plus, you had that recommendation before, and still do for listing:
> <dt><dfn><code>listing</code></dfn></dt>
> - <dt><dfn><code>xmp</code></dfn></dt>
> <dd><p>Use <code>pre</code> and <code>code</code> instead.</p></dd>
I'd be fine with "use pre instead" for both listing and xmp, though.
--
Simon Pieters
Opera Software
