[html5] r2267 - [e] (0) move from the 'big-issue' class to 'XXX'.

whatwg at whatwg.org whatwg at whatwg.org
Thu Oct 2 03:16:20 PDT 2008


Author: ianh
Date: 2008-10-02 03:16:19 -0700 (Thu, 02 Oct 2008)
New Revision: 2267

Modified:
   index
   source
Log:
[e] (0) move from the 'big-issue' class to 'XXX'.

Modified: index
===================================================================
--- index	2008-10-02 10:11:21 UTC (rev 2266)
+++ index	2008-10-02 10:16:19 UTC (rev 2267)
@@ -167,7 +167,7 @@
 
   <div id=stability></div>
 
-  <p class=big-issue>Some of the more major known issues are marked
+  <p class=XXX>Some of the more major known issues are marked
   like this. There are many other issues that have been raised as
   well; the issues given in this document are not the only known
   issues! Also, firing of events needs to be unified (right now some
@@ -1291,7 +1291,7 @@
 
   <p class=example>This is an example.</p>
 
-  <p class=big-issue>This is an open issue.</p>
+  <p class=XXX>This is an open issue.</p>
 
   <p class=warning>This is a warning.</p>
 
@@ -1848,7 +1848,7 @@
 
   <h4 id=features-defined-in-other-specifications><span class=secno>2.2.2 </span>Features defined in other specifications</h4>
 
-  <p class=big-issue>this section will be removed at some point</p>
+  <p class=XXX>this section will be removed at some point</p>
 
   <p>Some elements are defined in terms of their DOM
   <dfn id=textcontent><code>textContent</code></dfn> attribute. This is an attribute
@@ -1864,14 +1864,14 @@
   DOM3 Core. <a href=#refsDOM3CORE>[DOM3CORE]</a></p>
 
   <p>The term <dfn id=activation-behavior>activation behavior</dfn> is used as defined in the
-  DOM3 Events specification. <a href=#refsDOM3EVENTS>[DOM3EVENTS]</a> <span class=big-issue>At
+  DOM3 Events specification. <a href=#refsDOM3EVENTS>[DOM3EVENTS]</a> <span class=XXX>At
   the time of writing, DOM3 Events hadn't yet been updated to define
   that phrase.</span></p>
 
   <p id=alternate-style-sheets>The rules for handling alternative
   style sheets are defined in the CSS object model specification. <a href=#refsCSSOM>[CSSOM]</a></p>
 
-  <p class=big-issue>See <a href="http://dev.w3.org/cvsweb/~checkout~/csswg/cssom/Overview.html?content-type=text/html;%20charset=utf-8">http://dev.w3.org/cvsweb/~checkout~/csswg/cssom/Overview.html?content-type=text/html;%20charset=utf-8</a></p>
+  <p class=XXX>See <a href="http://dev.w3.org/cvsweb/~checkout~/csswg/cssom/Overview.html?content-type=text/html;%20charset=utf-8">http://dev.w3.org/cvsweb/~checkout~/csswg/cssom/Overview.html?content-type=text/html;%20charset=utf-8</a></p>
   <!--XXX empty title attribute is equivalent to missing attribute for
   purposes of alternate style sheet processing -->
 
@@ -1879,26 +1879,26 @@
   <h4 id=common-conformance-requirements-for-apis-exposed-to-javascript><span class=secno>2.2.3 </span>Common conformance requirements for APIs exposed to
   JavaScript</h4>
 
-  <p class=big-issue>This section will eventually be removed in favour of WebIDL.</p>
+  <p class=XXX>This section will eventually be removed in favour of WebIDL.</p>
 
-  <p class=big-issue>A lot of arrays/lists/<a href=#collections-0 title=collections>collection</a>s
+  <p class=XXX>A lot of arrays/lists/<a href=#collections-0 title=collections>collection</a>s
   in this spec assume zero-based indexes but use the term "<var title="">index</var>th" liberally. We should define those to be
   zero-based and be clearer about this.</p>
 
   <p>Unless otherwise specified, if a DOM attribute that is a floating
   point number type (<code title="">float</code>) is assigned an
-  Infinity or Not-a-Number value, a <code class=big-issue>NOT_SUPPORTED_ERR</code> exception must be
+  Infinity or Not-a-Number value, a <code class=XXX>NOT_SUPPORTED_ERR</code> exception must be
   raised.</p>
 
   <p>Unless otherwise specified, if a method with an argument that is a
   floating point number type (<code title="">float</code>) is passed
-  an Infinity or Not-a-Number value, a <code class=big-issue>NOT_SUPPORTED_ERR</code> exception must be
+  an Infinity or Not-a-Number value, a <code class=XXX>NOT_SUPPORTED_ERR</code> exception must be
   raised.</p>
 
   <!-- XXX DOMB -->
   <p>Unless otherwise specified, if a method is passed fewer
   arguments than is defined for that method in its IDL definition,
-  a <code class=big-issue>NOT_SUPPORTED_ERR</code> exception must be
+  a <code class=XXX>NOT_SUPPORTED_ERR</code> exception must be
   raised.</p>
 
   <!-- XXX DOMB -->
@@ -1953,7 +1953,7 @@
   <!-- XXX need to define how to handle U+000A LINE FEED and U+000D
   CARRIAGE RETURN in attributes (for HTML) -->
 
-  <p class=big-issue>Need to go through the whole spec and make sure
+  <p class=XXX>Need to go through the whole spec and make sure
   all the attribute values are clearly defined either in terms of
   microsyntaxes or in terms of other specs, or as "Text" or some
   such.</p>
@@ -2408,7 +2408,7 @@
 
   </ol><h5 id=percentages-and-dimensions><span class=secno>2.4.3.5 </span>Percentages and dimensions</h5>
 
-  <p class=big-issue><dfn id=valid-positive-non-zero-integers>valid positive non-zero integers</dfn>
+  <p class=XXX><dfn id=valid-positive-non-zero-integers>valid positive non-zero integers</dfn>
   <dfn id=rules-for-parsing-dimension-values>rules for parsing dimension values</dfn> (only used by
   height/width on img, embed, object — lengths in css pixels or
   percentages)</p>
@@ -2686,7 +2686,7 @@
 
   <h5 id=specific-moments-in-time><span class=secno>2.4.4.1 </span>Specific moments in time</h5>
 
-  <p class=big-issue>This syntax is going to be tightened up and
+  <p class=XXX>This syntax is going to be tightened up and
   made almost exactly the same as the <a href=#valid-utc-date-and-time-string>valid UTC date and time
   string</a> syntax, with the exception of allowing time zones. In
   fact what we might do is allow time zones in general, use the same
@@ -3254,9 +3254,9 @@
   consisting of a year, a month, a day, an hour, a minute, a second,
   and a fraction of a second. <a href=#refsGREGORIAN>[GREGORIAN]</a></p>
 
-  <p class=big-issue>... <dfn id=valid-utc-date-and-time-string>valid UTC date and time string</dfn></p>
+  <p class=XXX>... <dfn id=valid-utc-date-and-time-string>valid UTC date and time string</dfn></p>
 
-  <p class=big-issue>... rules to <dfn id=parse-a-utc-date-and-time-string>parse a UTC date and time
+  <p class=XXX>... rules to <dfn id=parse-a-utc-date-and-time-string>parse a UTC date and time
   string</dfn></p>
 
 
@@ -3267,9 +3267,9 @@
   consisting of a year, a month, a day, an hour, a minute, a second,
   and a fraction of a second. <a href=#refsGREGORIAN>[GREGORIAN]</a></p>
 
-  <p class=big-issue>... <dfn id=valid-local-date-and-time-string>valid local date and time string</dfn></p>
+  <p class=XXX>... <dfn id=valid-local-date-and-time-string>valid local date and time string</dfn></p>
 
-  <p class=big-issue>... rules to <dfn id=parse-a-local-date-and-time-string>parse a local date and time
+  <p class=XXX>... rules to <dfn id=parse-a-local-date-and-time-string>parse a local date and time
   string</dfn></p>
 
 
@@ -3279,9 +3279,9 @@
   Gregorian date with no timezone information, consisting of a year, a
   month, and a day. <a href=#refsGREGORIAN>[GREGORIAN]</a></p>
 
-  <p class=big-issue>... <dfn id=valid-date-string>valid date string</dfn></p>
+  <p class=XXX>... <dfn id=valid-date-string>valid date string</dfn></p>
 
-  <p class=big-issue>... rules to <dfn id=parse-a-date-string>parse a date string</dfn></p>
+  <p class=XXX>... rules to <dfn id=parse-a-date-string>parse a date string</dfn></p>
 
 
   <h5 id=months><span class=secno>2.4.4.6 </span>Months</h5>
@@ -3290,9 +3290,9 @@
   Gregorian date with no timezone information and no date information
   beyond a year and a month. <a href=#refsGREGORIAN>[GREGORIAN]</a></p>
 
-  <p class=big-issue>... <dfn id=valid-month-string>valid month string</dfn></p>
+  <p class=XXX>... <dfn id=valid-month-string>valid month string</dfn></p>
 
-  <p class=big-issue>... rules to <dfn id=parse-a-month-string>parse a month string</dfn></p>
+  <p class=XXX>... rules to <dfn id=parse-a-month-string>parse a month string</dfn></p>
 
 
   <h5 id=weeks><span class=secno>2.4.4.7 </span>Weeks</h5>
@@ -3303,9 +3303,9 @@
 
   <!-- XXX ISO week information -->
 
-  <p class=big-issue>... <dfn id=valid-week-string>valid week string</dfn></p>
+  <p class=XXX>... <dfn id=valid-week-string>valid week string</dfn></p>
 
-  <p class=big-issue>... rules to <dfn id=parse-a-week-string>parse a week string</dfn></p>
+  <p class=XXX>... rules to <dfn id=parse-a-week-string>parse a week string</dfn></p>
 
 
   <h5 id=times><span class=secno>2.4.4.8 </span>Times</h5>
@@ -3314,14 +3314,14 @@
   time with no timezone information, consisting of an hour, a minute,
   a second, and a fraction of a second.</p>
 
-  <p class=big-issue>... <dfn id=valid-time-string>valid time string</dfn></p>
+  <p class=XXX>... <dfn id=valid-time-string>valid time string</dfn></p>
 
-  <p class=big-issue>... rules to <dfn id=parse-a-time-string>parse a time string</dfn></p>
+  <p class=XXX>... rules to <dfn id=parse-a-time-string>parse a time string</dfn></p>
 
 
   <h5 id=time-offsets><span class=secno>2.4.4.9 </span>Time offsets</h5>
 
-  <p class=big-issue><dfn id=valid-time-offset>valid time offset</dfn>, <dfn id=rules-for-parsing-time-offsets>rules for
+  <p class=XXX><dfn id=valid-time-offset>valid time offset</dfn>, <dfn id=rules-for-parsing-time-offsets>rules for
   parsing time offsets</dfn>, <dfn id=time-offset-serialization-rules>time offset serialization
   rules</dfn>; probably in the format "5d4h3m2.1s" or similar, with
   all components being optional, and the last component's unit suffix
@@ -3446,7 +3446,7 @@
 
   <h4 id=comma-separated-tokens><span class=secno>2.4.6 </span>Comma-separated tokens</h4>
 
-  <p class=big-issue>We should allow whitespace around commas, and
+  <p class=XXX>We should allow whitespace around commas, and
   leading/trailing whitespace.</p>
 
   <p>A <dfn id=set-of-comma-separated-tokens>set of comma-separated tokens</dfn> is a set of zero or
@@ -4608,7 +4608,7 @@
      <td>Safe
      <td>A 0 word following by a 1 word, a Windows Icon file format signature.
 
-  </table><p class=big-issue>I'd like to add types like MPEG, AVI, Flash,
+  </table><p class=XXX>I'd like to add types like MPEG, AVI, Flash,
   Java, etc, to the above table.</p>
 
   <p>User agents may support further types if desired, by implicitly
@@ -4780,7 +4780,7 @@
 
    </li>
 
-   <li><p class=big-issue>If, before the next ">", you find two
+   <li><p class=XXX>If, before the next ">", you find two
    xmlns* attributes with http://www.w3.org/1999/02/22-rdf-syntax-ns#
    and http://purl.org/rss/1.0/ as the namespaces, then the sniffed
    type of the resource is "application/rss+xml", abort these
@@ -5124,7 +5124,7 @@
 
    <li>Return that <code>NodeList</code> object.</li>
 
-  </ol><!-- see also http://ln.hixie.ch/?start=1161042744&count=1 --><p class=big-issue>We may want to add <code>add()</code> and
+  </ol><!-- see also http://ln.hixie.ch/?start=1161042744&count=1 --><p class=XXX>We may want to add <code>add()</code> and
   <code>remove()</code> methods here too because IE implements
   HTMLSelectElement and HTMLOptionsCollection on the same object, and
   so people use them almost interchangeably in the wild.</p>
@@ -5257,7 +5257,7 @@
   values from names, one for setting names to certain values, and one
   for deleting names.</p>
 
-  <p class=big-issue>The names of the methods on this interface are
+  <p class=XXX>The names of the methods on this interface are
   temporary and will be fixed when the Web IDL / "Language Bindings
   for DOM Specifications" spec is ready to handle this case.</p>
 
@@ -5320,7 +5320,7 @@
 
   <p><em>This section is non-normative.</em></p>
 
-  <p class=big-issue>An introduction to marking up a document.</p>
+  <p class=XXX>An introduction to marking up a document.</p>
 
 
   <h3 id=documents><span class=secno>3.2 </span>Documents</h3>
@@ -5542,7 +5542,7 @@
   <a href=#quirks-mode>quirks mode</a> by the <a href=#html-parser>HTML parser</a>, in which
   case it must instead return the literal string "<code title="">BackCompat</code>".</p>
 
-  <div class=big-issue>
+  <div class=XXX>
 
    <p>As far as parsing goes, the quirks I know of are:</p>
 
@@ -6670,7 +6670,7 @@
   all cross-references. Some of them refer specifically to the
   activation behavior stuff. -->
 
-  <p class=big-issue>Parts of this section should eventually be
+  <p class=XXX>Parts of this section should eventually be
   moved to DOM3 Events.</p> <!-- but see comment above -->
 
 <!--
@@ -7006,12 +7006,12 @@
 
    </li>
 
-   <li><p class=big-issue>onbeforeunload, onunload, reset timers, empty event queue, kill any pending transactions, XMLHttpRequests, etc</li>
+   <li><p class=XXX>onbeforeunload, onunload, reset timers, empty event queue, kill any pending transactions, XMLHttpRequests, etc</li>
    <!-- http://software.hixie.ch/utilities/js/live-dom-viewer/?%3C!DOCTYPE%20html%3E...%3Ciframe%20src%3D%22document%22%3E%3C%2Fiframe%3E%0A%3Cscript%3Eonload%20%3D%20function%20()%20{%20f%20%3D%20document.getElementsByTagName(%27iframe%27)[0]%3B%20d%20%3D%20f.contentDocument%3B%20}%3C%2Fscript%3E%0A%3Cinput%20type%3Dbutton%20onclick%3D%22w(d.documentElement.innerHTML)%22%20value%3D%22dump%22%3E%0A%3Cinput%20type%3Dbutton%20onclick%3D%22d.body.bgColor%3D%27red%27%22%20value%3D%22color%22%3E%0A%3Cinput%20type%3Dbutton%20onclick%3D%22f.style.border%3D%27lime%20solid%27%22%20value%3D%22color%20frame%22%3E%0A%3Cinput%20type%3Dbutton%20onclick%3D%22d.open()%3B%20d.write(%27%3Cp%3Etest%3C%2Fp%3E%27)%3B%20d.close()%22%20value%3D%22replace%22%3E%0A%3Cinput%20type%3Dbutton%20onclick%3D%22d.open()%3B%20d.write(%27%3Cp%3E%3Cscript%3Ei%20%3D%200%3B%20setInterval(%26quot%3Bparent.w(i%2B%2B)%26quot%3B%2C%20500)%3C%2Fscript%3E%3C%2Fp%3E%27)%3B%20d.close()%22%20value%3D%22replace%20with%20timer%22%3E%0A -->
 
    <li><p>If the document has an <span>active parser</span><!--XXX
    xref-->, then stop that parser, and throw away any pending content
-   in the input stream. <span class=big-issue>what about if it
+   in the input stream. <span class=XXX>what about if it
    doesn't, because it's either like a text/plain, or Atom, or PDF, or
    XHTML, or image document, or something?</span></li><!-- XXX see
    also innerHTML in HTML -->
@@ -7171,7 +7171,7 @@
 
     <p>If the document has an <span>active parser</span><!--XXX
     xref-->, then stop that parser, and throw away any pending content
-    in the input stream. <span class=big-issue>what about if it
+    in the input stream. <span class=XXX>what about if it
     doesn't, because it's either like a text/plain, or Atom, or PDF,
     or XHTML, or image document, or something?</span></p><!-- XXX see
     also document.open() -->
@@ -8443,7 +8443,7 @@
 
    <dd>
 
-    <ol><li class=big-issue>...</li>
+    <ol><li class=XXX>...</li>
 
     </ol></dd>
 
@@ -8785,7 +8785,7 @@
   getting, and forward the new value to that same attribute on
   setting.</p>
 
-  <!-- <p class="big-issue">Need more here - defining preferred
+  <!-- <p class="XXX">Need more here - defining preferred
   stylesheets, alternative stylesheets, persistent stylesheets, ordering
   of stylesheets, dynamic additions/removals, how it maps to
   .styleSheets, HTTP Link: headers, and the stuff about the alternative
@@ -9059,7 +9059,7 @@
      scripts that will execute when the document has finished
      parsing</a>.
  
-     <span class=big-issue>This isn't compatible with IE for inline
+     <span class=XXX>This isn't compatible with IE for inline
      deferred scripts, but then what IE does is pretty hard to pin down
      exactly. Do we want to keep this like it is? Be more compatible?</span>
      <!--XXX  
@@ -9244,7 +9244,7 @@
         given by <var><a href="#the-script's-character-encoding">the script's character encoding</a></var>, regardless
         of any metadata given by the file's <a href=#content-type-0 title=Content-Type>Content-Type metadata</a>.</p>
 
-        <p class=big-issue>This means that a UTF-16 document will
+        <p class=XXX>This means that a UTF-16 document will
         always assume external scripts are UTF-16...? This applies,
         e.g., to document's created using createDocument()... It also
         means changing document.charSet will affect the character
@@ -11364,7 +11364,7 @@
 
   <ol><li><p>If the <code title=event-DOMActivate>DOMActivate</code>
    event in question is not <span title=concept-events-trusted>trusted</span> (i.e. a <code title=dom-click><a href=#dom-click>click()</a></code> method call was the reason for the
-   event being dispatched), and the <code><a href=#the-a-element>a</a></code> element's <code title=attr-hyperlink-target><a href=#attr-hyperlink-target>target</a></code> attribute is <span class=big-issue>...</span> then raise an
+   event being dispatched), and the <code><a href=#the-a-element>a</a></code> element's <code title=attr-hyperlink-target><a href=#attr-hyperlink-target>target</a></code> attribute is <span class=XXX>...</span> then raise an
    <code>INVALID_ACCESS_ERR</code> exception and abort these
    steps.</li>
 
@@ -11836,7 +11836,7 @@
   part of the document that has been highlighted due to its likely
   relevance to the user's current activity.</p>
 
-  <p class=big-issue>The rendering section will eventually suggest
+  <p class=XXX>The rendering section will eventually suggest
   that user agents provide a way to let users jump between
   <code><a href=#the-mark-element>mark</a></code> elements. Suggested rendering is a neon yellow
   background highlight, though UAs maybe should allow this to be
@@ -12224,7 +12224,7 @@
 
   </div>
 
-  <p class=big-issue>These APIs may be suboptimal. Comments on
+  <p class=XXX>These APIs may be suboptimal. Comments on
   making them more useful to JS authors are welcome. The primary use
   cases for these elements are for marking up publication dates
   e.g. in blog entries, and for marking event dates in hCalendar
@@ -12388,7 +12388,7 @@
   attributes must return zero. The value parsed from the
   <code><a href=#textcontent>textContent</a></code> never affects the DOM values.</p>
 
-  <p class=big-issue>Would be cool to have the <code title=dom-progress-value><a href=#dom-progress-value>value</a></code> DOM attribute update the
+  <p class=XXX>Would be cool to have the <code title=dom-progress-value><a href=#dom-progress-value>value</a></code> DOM attribute update the
   <code><a href=#textcontent>textContent</a></code> in-line...</p>
 
   <p>If the progress bar is an indeterminate progress bar, then the
@@ -12749,7 +12749,7 @@
   attributes must return zero. The value parsed from the
   <code><a href=#textcontent>textContent</a></code> never affects the DOM values.</p>
 
-  <p class=big-issue>Would be cool to have the <code title=dom-meter-value><a href=#dom-meter-value>value</a></code> DOM attribute update the
+  <p class=XXX>Would be cool to have the <code title=dom-meter-value><a href=#dom-meter-value>value</a></code> DOM attribute update the
   <code><a href=#textcontent>textContent</a></code> in-line...</p>
 
 <!-- XXX
@@ -13301,7 +13301,7 @@
 
   <h4 id=usage-summary><span class=secno>4.6.25 </span>Usage summary</h4>
 
-  <p class=big-issue>We need to summarize the various elements, in
+  <p class=XXX>We need to summarize the various elements, in
   particular to distinguish b/i/em/strong/var/q/mark/cite.</p>
 
   <!-- XXX when you do this, also reorder the elements in this section
@@ -13849,7 +13849,7 @@
   attribute's value are described <a href=#alt>in the next
   section</a>.</p>
 
-  <p class=big-issue>There has been some suggestion that the <code title="">longdesc</code> attribute from HTML4, or some other
+  <p class=XXX>There has been some suggestion that the <code title="">longdesc</code> attribute from HTML4, or some other
   mechanism that is more powerful than <code title="">alt=""</code>,
   should be included. This has not yet been considered.</p>
 
@@ -15319,7 +15319,7 @@
 
    </li>
 
-  </ul><p class=big-issue>Parts of the above might get moved into the
+  </ul><p class=XXX>Parts of the above might get moved into the
   rendering section at some point.</p>
 
   <p>If the attribute is not specified, or if the <a href=#origin-0>origin</a>
@@ -15370,7 +15370,7 @@
   that could act as fallback content.)</p>
 
   <p>The content model of <code><a href=#the-iframe-element>iframe</a></code> elements is text, except
-  that the text must be such that <span class=big-issue>... anyone
+  that the text must be such that <span class=XXX>... anyone
   have any bright ideas?</span></p>
   <!--XXX
     Gotta handle <script> elements inside <iframe>s that screw around with the DOM on the fly, or that use document.write().
@@ -15500,7 +15500,7 @@
     handle resources with <a href=#url-path title=url-path><path></a>
     components that end with the four character string "<code title="">.swf</code>".</p>
 
-    <p class=big-issue>It would be better if browsers didn't do
+    <p class=XXX>It would be better if browsers didn't do
     extension sniffing like this, and only based their decision on the
     actual contents of the resource. Couldn't we just apply the
     <span>sniffed type of a resource</span> steps?</p>
@@ -15773,7 +15773,7 @@
         to the value of this attribute; otherwise, the <a href=#browsing-context-name>browsing
         context name</a> must be set to the empty string.</p>
 
-        <p class=big-issue>navigation might end up treating it as
+        <p class=XXX>navigation might end up treating it as
         something else, because it can do sniffing. how should we
         handle that?</p>
 
@@ -16211,7 +16211,7 @@
   provided to easily allow the user to obtain a full-screen playback
   mode.</p>
 
-  <p class=big-issue>The spec does not currently define the
+  <p class=XXX>The spec does not currently define the
   interaction of the "controls" attribute with the "height" and
   "width" attributes. This will likely be defined in the rendering
   section based on implementation experience. So far, browsers seem to
@@ -16225,7 +16225,7 @@
   <p>User agents may support any video and audio codecs and container
   formats.</p>
 
-  <p class=big-issue>It would be helpful for interoperability if all
+  <p class=XXX>It would be helpful for interoperability if all
   browsers could support the same codecs. However, there are no known
   codecs that satisfy all the current players: we need a codec that is
   known to not require per-unit or per-distributor licensing, that is
@@ -17076,7 +17076,7 @@
       be optimally rendered must cause the user agent to execute the
       following steps.</p>
 
-      <ol><li class=big-issue>Should we fire a 'warning' event? Set the
+      <ol><li class=XXX>Should we fire a 'warning' event? Set the
        'error' flag to 'MEDIA_ERR_SUBOPTIMAL' or something?</li>
 
       </ol></dd>
@@ -18187,7 +18187,7 @@
      <td>
   </table><h5 id=security-and-privacy-considerations><span class=secno>4.8.10.14 </span>Security and privacy considerations</h5>
 
-  <p class=big-issue>Talk about making sure interactive media files
+  <p class=XXX>Talk about making sure interactive media files
   (e.g. SVG) don't have access to the container DOM (XSS potential);
   talk about not exposing any sensitive data like metadata from tracks
   in the media files (intranet snooping risk)</p>
@@ -19740,7 +19740,7 @@
    characters</span> in <var title="">text</var> with U+0020 SPACE
    characters.</p></li>
 
-   <li><p>Form a <em class="big-issue">whatever CSS ends up calling
+   <li><p>Form a <em class="XXX">whatever CSS ends up calling
    vertical line boxes and inline boxes</em> containing the text <var
    title="">text</var>, with all the properties at their initial
    values except the 'font' property of the inline box set to <var
@@ -19752,7 +19752,7 @@
    final words - ->
 
    <li><p>If the <var title="">maxHeight</var> argument was specified
-   and the hypothetical height of the <em class="big-issue">box</em>
+   and the hypothetical height of the <em class="XXX">box</em>
    in the hypothetical line box is greater than <var
    title="">maxHeight</var> CSS pixels, then change <var
    title="">font</var> to have a more condensed font (if one is
@@ -19763,7 +19763,7 @@
    <li>
 
     <p>Let the <var title="">anchor point</var> be a point on the <em
-    class="big-issue">inline box</var>, determined by the <code
+    class="XXX">inline box</var>, determined by the <code
     title="dom-context-2d-textAlign">textAlign</code>, as follows:</p>
 
     <p>Vertical position:</p>
@@ -19783,7 +19783,7 @@
      <code>canvas</code> element is 'rtl'</dt>
 
      <dd>Let the <var title="">anchor point</var>'s vertical
-     position be the top edge of the <em class="big-issue">inline
+     position be the top edge of the <em class="XXX">inline
      box</em>.</dd>
 
      <dt> If <code
@@ -19799,7 +19799,7 @@
      <code>canvas</code> element is 'rtl'</dt>
 
      <dd>Let the <var title="">anchor point</var>'s vertical
-     position be the bottom edge of the <em class="big-issue">inline
+     position be the bottom edge of the <em class="XXX">inline
      box</em>.</dd>
 
 
@@ -19809,13 +19809,13 @@
 
      <dd>Let the <var title="">anchor point</var>'s vertical position
      be half way between the top and bottom edges of the <em
-     class="big-issue">inline box</em>.</dd>
+     class="XXX">inline box</em>.</dd>
 
     </dl>
 
     <p>Let the horizontal position be half way between the left and
     right edges of the em box of the first available font of the <em
-    class="big-issue">inline box</em>.</p>
+    class="XXX">inline box</em>.</p>
 
    </li>
 
@@ -20042,7 +20042,7 @@
   integer using the IEEE 754r <i>convertToIntegerTiesToEven</i>
   rounding mode.  <a href=#refsECMA262>[ECMA262]</a> <a href=#refsIEEE754r>[IEEE754R]</a></p>
 
-  <p class=big-issue>The above is not intended to cause these
+  <p class=XXX>The above is not intended to cause these
   methods to get any unusual behaviour, it's just supposed to be the
   normal behaviour for passing values to a method expecting an <code title="">octet</code> type.</p>
 
@@ -20275,7 +20275,7 @@
   </ol><!-- XXX add xrefs in the list above --><!--
   <h5 id="3d">The 3D context</h5>
 
-  <p class="big-issue">Well, one day.</p>
+  <p class="XXX">Well, one day.</p>
 --><h5 id=color-spaces-and-color-correction><span class=secno>4.8.11.2 </span>Color spaces and color correction</h5>
 
   <p>The <code><a href=#the-canvas-element>canvas</a></code> APIs must perform color correction at
@@ -20571,7 +20571,7 @@
 
   <ol><li>If the <code title=event-DOMActivate>DOMActivate</code> event
    in question is not <span title=concept-events-trusted>trusted</span> (i.e. a <code title=dom-click><a href=#dom-click>click()</a></code> method call was the reason for the
-   event being dispatched), and the <code><a href=#the-area-element>area</a></code> element's <code title=attr-area-target>target</code> attribute is <span class=big-issue>...</span> then raise an
+   event being dispatched), and the <code><a href=#the-area-element>area</a></code> element's <code title=attr-area-target>target</code> attribute is <span class=XXX>...</span> then raise an
    <code>INVALID_ACCESS_ERR</code> exception.</li>
 
    <li>Otherwise, the user agent must <a href=#following-hyperlinks title="following
@@ -20937,7 +20937,7 @@
 
   <p><em>This section is non-normative.</em></p>
 
-  <p class=big-issue>...examples, how to write tables accessibly, a
+  <p class=XXX>...examples, how to write tables accessibly, a
   brief mention of the table model, etc...</p>
 
 
@@ -20980,7 +20980,7 @@
   </dl><p>The <code><a href=#the-table-element>table</a></code> element represents data with more than one
   dimension (a <a href=#concept-table title=concept-table>table</a>).</p>
 
-  <p class=big-issue>we need some editorial text on how layout
+  <p class=XXX>we need some editorial text on how layout
   tables are bad practice and non-conforming</p>
 
   <p>The children of a <code><a href=#the-table-element>table</a></code> element must be, in
@@ -23768,7 +23768,7 @@
   <p>When an <code><a href=#the-input-element>input</a></code> element's <code title=attr-input-type><a href=#attr-input-type>type</a></code> attribute is in the <a href=#hidden-state title=attr-input-type-hidden>Hidden</a> state, the rules in
   this section apply.</p>
 
-  <p class=big-issue>...</p>
+  <p class=XXX>...</p>
 
   <p><strong>Constraint validation:</strong> If an <code><a href=#the-input-element>input</a></code>
   element's <code title=attr-input-type><a href=#attr-input-type>type</a></code> attribute is in
@@ -25035,7 +25035,7 @@
   <p>When an <code><a href=#the-input-element>input</a></code> element's <code title=attr-input-type><a href=#attr-input-type>type</a></code> attribute is in the <a href=#file-state title=attr-input-type-file>File</a> state, the rules in this
   section apply.</p>
 
-  <p class=big-issue>...</p>
+  <p class=XXX>...</p>
 
   <p>The <dfn id=attr-input-accept title=attr-input-accept><code>accept</code></dfn>
   attribute may be specified to provide user agents with a hint of
@@ -25067,7 +25067,7 @@
 
   <!-- XXX the selected file(s) must either have the given types or be of the given category -->
 
-  <p class=big-issue>... list of <dfn id=concept-input-type-file-selected title=concept-input-type-file-selected>selected files</dfn></p>
+  <p class=XXX>... list of <dfn id=concept-input-type-file-selected title=concept-input-type-file-selected>selected files</dfn></p>
 
 
 
@@ -25076,7 +25076,7 @@
   <p>When an <code><a href=#the-input-element>input</a></code> element's <code title=attr-input-type><a href=#attr-input-type>type</a></code> attribute is in the <a href=#submit-button-state title=attr-input-type-submit>Submit Button</a> state, the rules
   in this section apply.</p>
 
-  <p class=big-issue>...</p>
+  <p class=XXX>...</p>
 
 <!--XXX
 rel="" on submit buttons?
@@ -25089,13 +25089,13 @@
   <p>When an <code><a href=#the-input-element>input</a></code> element's <code title=attr-input-type><a href=#attr-input-type>type</a></code> attribute is in the <a href=#image-button-state title=attr-input-type-image>Image Button</a> state, the rules
   in this section apply.</p>
 
-  <p class=big-issue>...</p>
+  <p class=XXX>...</p>
 
-  <p class=big-issue>... <dfn id=attr-input-alt title=attr-input-alt><code>alt</code></dfn></p>
+  <p class=XXX>... <dfn id=attr-input-alt title=attr-input-alt><code>alt</code></dfn></p>
 
-  <p class=big-issue>... <dfn id=attr-input-src title=attr-input-src><code>src</code></dfn></p>
+  <p class=XXX>... <dfn id=attr-input-src title=attr-input-src><code>src</code></dfn></p>
 
-  <p class=big-issue>... image: <dfn id=concept-input-type-image-coordinate title=concept-input-type-image-coordinate>selected coordinate</dfn></p>
+  <p class=XXX>... image: <dfn id=concept-input-type-image-coordinate title=concept-input-type-image-coordinate>selected coordinate</dfn></p>
 
 
 
@@ -25104,7 +25104,7 @@
   <p>When an <code><a href=#the-input-element>input</a></code> element's <code title=attr-input-type><a href=#attr-input-type>type</a></code> attribute is in the <a href=#reset-button-state title=attr-input-type-reset>Reset Button</a> state, the rules
   in this section apply.</p>
 
-  <p class=big-issue>...</p>
+  <p class=XXX>...</p>
 
   <p><strong>Constraint validation:</strong> If an <code><a href=#the-input-element>input</a></code>
   element's <code title=attr-input-type><a href=#attr-input-type>type</a></code> attribute is in
@@ -25118,7 +25118,7 @@
   <p>When an <code><a href=#the-input-element>input</a></code> element's <code title=attr-input-type><a href=#attr-input-type>type</a></code> attribute is in the <a href=#button-state title=attr-input-type-button>Button</a> state, the rules in
   this section apply.</p>
 
-  <p class=big-issue>...</p>
+  <p class=XXX>...</p>
 
   <p><strong>Constraint validation:</strong> If an <code><a href=#the-input-element>input</a></code>
   element's <code title=attr-input-type><a href=#attr-input-type>type</a></code> attribute is in
@@ -25211,7 +25211,7 @@
 
   <h6 id=the-list-attribute><span class=secno>4.10.4.2.2 </span>The <code title=attr-input-list><a href=#attr-input-list>list</a></code> attribute</h6>
 
-  <p class=big-issue>... <dfn id=attr-input-list title=attr-input-list><code>list</code></dfn></p>
+  <p class=XXX>... <dfn id=attr-input-list title=attr-input-list><code>list</code></dfn></p>
 
 
 
@@ -25229,13 +25229,13 @@
 
   <h6 id=the-size-attribute><span class=secno>4.10.4.2.4 </span>The <code title=attr-input-size><a href=#attr-input-size>size</a></code> attribute</h6>
 
-  <p class=big-issue>... <dfn id=attr-input-size title=attr-input-size><code>size</code></dfn></p>
+  <p class=XXX>... <dfn id=attr-input-size title=attr-input-size><code>size</code></dfn></p>
 
 
 
   <h6 id=the-required-attribute><span class=secno>4.10.4.2.5 </span>The <code title=attr-input-required><a href=#attr-input-required>required</a></code> attribute</h6>
 
-  <p class=big-issue>... <dfn id=attr-input-required title=attr-input-required><code>required</code></dfn></p>
+  <p class=XXX>... <dfn id=attr-input-required title=attr-input-required><code>required</code></dfn></p>
 
 
 
@@ -25276,7 +25276,7 @@
 
   <h6 id=the-pattern-attribute><span class=secno>4.10.4.2.7 </span>The <code title=attr-input-pattern><a href=#attr-input-pattern>pattern</a></code> attribute</h6>
 
-  <p class=big-issue>... <dfn id=attr-input-pattern title=attr-input-pattern><code>pattern</code></dfn></p>
+  <p class=XXX>... <dfn id=attr-input-pattern title=attr-input-pattern><code>pattern</code></dfn></p>
 
 
 
@@ -25526,8 +25526,8 @@
    <li><p>Set the <a href=#concept-fe-value title=concept-fe-value>value</a> of the
    element to <var title="">value as string</var>.</li>
 
-  </ol><hr><p class=big-issue>... <dfn id=dom-input-list title=dom-input-list><code>list</code></dfn></p>
-  <p class=big-issue>... <dfn id=dom-input-selectedoption title=dom-input-selectedOption><code>selectedOption</code></dfn></p>
+  </ol><hr><p class=XXX>... <dfn id=dom-input-list title=dom-input-list><code>list</code></dfn></p>
+  <p class=XXX>... <dfn id=dom-input-selectedoption title=dom-input-selectedOption><code>selectedOption</code></dfn></p>
 
 
 
@@ -25576,7 +25576,7 @@
   void <a href=#dom-cva-setcustomvalidity title=dom-cva-setCustomValidity>setCustomValidity</a>(in DOMString error);
 };</pre>
    </dd> 
-  </dl><p class=big-issue>...</p>
+  </dl><p class=XXX>...</p>
 
   <p>The <code title=attr-fae-form><a href=#attr-fae-form>form</a></code> attribute is used to
   explicitly associate the <code><a href=#the-button-element>button</a></code> element with its
@@ -25642,7 +25642,7 @@
   void <a href=#dom-cva-setcustomvalidity title=dom-cva-setCustomValidity>setCustomValidity</a>(in DOMString error);
 };</pre>
    </dd> 
-  </dl><p class=big-issue>...</p>
+  </dl><p class=XXX>...</p>
 
   <p>The <code title=attr-fae-form><a href=#attr-fae-form>form</a></code> attribute is used to
   explicitly associate the <code><a href=#the-select-element>select</a></code> element with its
@@ -25676,7 +25676,7 @@
   readonly attribute <a href=#htmloptionscollection-0>HTMLOptionsCollection</a> <span title=dom-select-options>options</span>;
 };</pre>
    </dd> 
-  </dl><p class=big-issue>...</p>
+  </dl><p class=XXX>...</p>
 
   <p><strong>Constraint validation:</strong> If an element has a
   <code><a href=#the-datalist-element>datalist</a></code> element ancestor, it is <a href=#barred-from-constraint-validation>barred from
@@ -25701,7 +25701,7 @@
            attribute DOMString <span title=dom-optgroup-label>label</span>;
 };</pre>
    </dd> 
-  </dl><p class=big-issue>...</p>
+  </dl><p class=XXX>...</p>
 
 
   <h4 id=the-option-element><span class=secno>4.10.9 </span>The <dfn><code>option</code></dfn> element</h4>
@@ -25736,13 +25736,13 @@
   readonly attribute long <span title=dom-option-index>index</span>;
 };</pre>
    </dd> 
-  </dl><p class=big-issue>...</p>
+  </dl><p class=XXX>...</p>
 
-  <p class=big-issue>... <dfn id=concept-option-selected title=concept-option-selected>selected</dfn></p>
+  <p class=XXX>... <dfn id=concept-option-selected title=concept-option-selected>selected</dfn></p>
 
-  <p class=big-issue>... <dfn id=concept-option-value title=concept-option-value>value</dfn></p>
+  <p class=XXX>... <dfn id=concept-option-value title=concept-option-value>value</dfn></p>
 
-  <p class=big-issue>
+  <p class=XXX>
    <dfn id=dom-option title=dom-option><code>Option()</code></dfn>
    <dfn id=dom-option-n title=dom-option-n><code>Option(<var title="">name</var>)</code></dfn>
    <dfn id=dom-option-nv title=dom-option-nv><code>Option(<var title="">name</var>, <var title="">value</var>)</code></dfn>
@@ -25803,7 +25803,7 @@
   void <a href=#dom-cva-setcustomvalidity title=dom-cva-setCustomValidity>setCustomValidity</a>(in DOMString error);
 };</pre>
    </dd> 
-  </dl><!-- XXX add selectionStart and company --><p class=big-issue>...</p>
+  </dl><!-- XXX add selectionStart and company --><p class=XXX>...</p>
 
   <p>The <code title=attr-fae-form><a href=#attr-fae-form>form</a></code> attribute is used to
   explicitly associate the <code><a href=#the-textarea-element>textarea</a></code> element with its
@@ -25855,7 +25855,7 @@
   void <a href=#dom-cva-setcustomvalidity title=dom-cva-setCustomValidity>setCustomValidity</a>(in DOMString error);
 };</pre>
    </dd> 
-  </dl><p class=big-issue>...</p>
+  </dl><p class=XXX>...</p>
 
   <p>The <code title=attr-fae-form><a href=#attr-fae-form>form</a></code> attribute is used to
   explicitly associate the <code><a href=#the-output-element>output</a></code> element with its
@@ -25962,9 +25962,9 @@
 
   <h5 id=naming-form-controls><span class=secno>4.10.13.1 </span>Naming form controls</h5>
 
-  <p class=big-issue>... <dfn id=attr-fe-name title=attr-fe-name>name</dfn> content attribute</p>
+  <p class=XXX>... <dfn id=attr-fe-name title=attr-fe-name>name</dfn> content attribute</p>
 
-  <p class=big-issue>... <dfn id=dom-fe-name title=dom-fe-name>name</dfn> DOM attribute</p>
+  <p class=XXX>... <dfn id=dom-fe-name title=dom-fe-name>name</dfn> DOM attribute</p>
 
   <p><strong>Constraint validation:</strong> If an element does not
   have a <code title=attr-fe-name><a href=#attr-fe-name>name</a></code> attribute specified,
@@ -25976,13 +25976,13 @@
 
   <h5 id=enabling-and-disabling-form-controls><span class=secno>4.10.13.2 </span>Enabling and disabling form controls</h5>
 
-  <p class=big-issue>... <dfn id=concept-fe-disabled title=concept-fe-disabled>disabled</dfn></p>
+  <p class=XXX>... <dfn id=concept-fe-disabled title=concept-fe-disabled>disabled</dfn></p>
   <!-- XXX remember to check for a fieldset ancestor that has its
   disabled attribute set, and always be disabled if you find one -->
 
-  <p class=big-issue>... <dfn id=attr-fe-disabled title=attr-fe-disabled>disabled</dfn> content attribute</p>
+  <p class=XXX>... <dfn id=attr-fe-disabled title=attr-fe-disabled>disabled</dfn> content attribute</p>
 
-  <p class=big-issue>... <dfn id=dom-fe-disabled title=dom-fe-disabled>disabled</dfn> DOM attribute</p>
+  <p class=XXX>... <dfn id=dom-fe-disabled title=dom-fe-disabled>disabled</dfn> DOM attribute</p>
 
   <p><strong>Constraint validation:</strong> If an element is <a href=#concept-fe-disabled title=concept-fe-disabled>disabled</a>, it is <a href=#barred-from-constraint-validation>barred from
   constraint validation</a>.</p>
@@ -25991,8 +25991,8 @@
 
   <h5 id="a-form-control's-value"><span class=secno>4.10.13.3 </span>A form control's value</h5>
 
-  <p class=big-issue>... <dfn id=concept-fe-value title=concept-fe-value>value</dfn></p>
-  <p class=big-issue>... <dfn id=concept-fe-checked title=concept-fe-checked>checkedness</dfn></p>
+  <p class=XXX>... <dfn id=concept-fe-value title=concept-fe-value>value</dfn></p>
+  <p class=XXX>... <dfn id=concept-fe-checked title=concept-fe-checked>checkedness</dfn></p>
   <!-- XXX autocomplete: define somewhere that the value may be set from a stored value -->
 
 
@@ -26043,30 +26043,30 @@
 
   <h4 id=attributes-for-form-submission><span class=secno>4.10.14 </span><dfn>Attributes for form submission</dfn></h4>
 
-  <p class=big-issue>... <dfn id=attr-fs-action title=attr-fs-action>action</dfn> content attribute</p>
+  <p class=XXX>... <dfn id=attr-fs-action title=attr-fs-action>action</dfn> content attribute</p>
 
-  <p class=big-issue>... <dfn id=dom-fs-action title=dom-fs-action>action</dfn> DOM attribute</p>
+  <p class=XXX>... <dfn id=dom-fs-action title=dom-fs-action>action</dfn> DOM attribute</p>
 
-  <p class=big-issue>... <dfn id=concept-fs-action title=concept-fs-action>action</dfn> if present else form's else default</p>
+  <p class=XXX>... <dfn id=concept-fs-action title=concept-fs-action>action</dfn> if present else form's else default</p>
   <!-- XXX mozilla bug 297761 -->
 
-  <p class=big-issue>... <dfn id=attr-fs-method title=attr-fs-method>method</dfn> content attribute</p>
+  <p class=XXX>... <dfn id=attr-fs-method title=attr-fs-method>method</dfn> content attribute</p>
 
-  <p class=big-issue>... <dfn id=dom-fs-method title=dom-fs-method>method</dfn> DOM attribute</p>
+  <p class=XXX>... <dfn id=dom-fs-method title=dom-fs-method>method</dfn> DOM attribute</p>
 
-  <p class=big-issue>... <dfn id=concept-fs-method title=concept-fs-method>method</dfn> if present else form's else default</p>
+  <p class=XXX>... <dfn id=concept-fs-method title=concept-fs-method>method</dfn> if present else form's else default</p>
 
-  <p class=big-issue>... <dfn id=attr-fs-enctype title=attr-fs-enctype>enctype</dfn> content attribute</p>
+  <p class=XXX>... <dfn id=attr-fs-enctype title=attr-fs-enctype>enctype</dfn> content attribute</p>
 
-  <p class=big-issue>... <dfn id=dom-fs-enctype title=dom-fs-enctype>enctype</dfn> DOM attribute</p>
+  <p class=XXX>... <dfn id=dom-fs-enctype title=dom-fs-enctype>enctype</dfn> DOM attribute</p>
 
-  <p class=big-issue>... <dfn id=concept-fs-enctype title=concept-fs-enctype>enctype</dfn> if present else form's else default</p>
+  <p class=XXX>... <dfn id=concept-fs-enctype title=concept-fs-enctype>enctype</dfn> if present else form's else default</p>
 
-  <p class=big-issue>... <dfn id=attr-fs-target title=attr-fs-target>target</dfn> content attribute</p>
+  <p class=XXX>... <dfn id=attr-fs-target title=attr-fs-target>target</dfn> content attribute</p>
 
-  <p class=big-issue>... <dfn id=dom-fs-target title=dom-fs-target>target</dfn> DOM attribute</p>
+  <p class=XXX>... <dfn id=dom-fs-target title=dom-fs-target>target</dfn> DOM attribute</p>
 
-  <p class=big-issue>... <dfn id=concept-fs-target title=concept-fs-target>target</dfn> if present else form's else base target else default</p> <!-- c.f. hyperlink following -->
+  <p class=XXX>... <dfn id=concept-fs-target title=concept-fs-target>target</dfn> if present else form's else base target else default</p> <!-- c.f. hyperlink following -->
 
   <p>Attributes for form submission can be specified both on
   <code><a href=#the-form-element>form</a></code> elements and on elements that represent buttons
@@ -26088,19 +26088,19 @@
   constraint validation</a> if it is an <code><a href=#the-output-element>output</a></code> or
   <code><a href=#the-fieldset-element>fieldset</a></code> element.)</p>
 
-  <p class=big-issue>An element <dfn id=concept-fv-valid title=concept-fv-valid>satisfies its constraints</dfn> if ...</p>
+  <p class=XXX>An element <dfn id=concept-fv-valid title=concept-fv-valid>satisfies its constraints</dfn> if ...</p>
 
-  <p class=big-issue>... <dfn id=suffering-from-a-type-mismatch>suffering from a type
+  <p class=XXX>... <dfn id=suffering-from-a-type-mismatch>suffering from a type
   mismatch</dfn></p>
 
-  <p class=big-issue>... <dfn id=suffering-from-being-too-long>suffering from being too
+  <p class=XXX>... <dfn id=suffering-from-being-too-long>suffering from being too
   long</dfn></p>
 
-  <p class=big-issue>... <dfn id=suffering-from-an-underflow>suffering from an underflow</dfn></p>
+  <p class=XXX>... <dfn id=suffering-from-an-underflow>suffering from an underflow</dfn></p>
 
-  <p class=big-issue>... <dfn id=suffering-from-an-overflow>suffering from an overflow</dfn></p>
+  <p class=XXX>... <dfn id=suffering-from-an-overflow>suffering from an overflow</dfn></p>
 
-  <p class=big-issue>... <dfn id=suffering-from-a-step-mismatch>suffering from a step
+  <p class=XXX>... <dfn id=suffering-from-a-step-mismatch>suffering from a step
   mismatch</dfn></p>
 
 
@@ -26193,7 +26193,7 @@
   conditions are <a href=#barred-from-constraint-validation title="barred from constraint
   validation">barring it from constraint validation</a>).</p>
 
-  <p class=big-issue> <dfn id=dom-cva-validity title=dom-cva-validity><code>validity</code></dfn> <dfn id=dom-cva-validationmessage title=dom-cva-validationMessage><code>validationMessage</code></dfn>
+  <p class=XXX> <dfn id=dom-cva-validity title=dom-cva-validity><code>validity</code></dfn> <dfn id=dom-cva-validationmessage title=dom-cva-validationMessage><code>validationMessage</code></dfn>
   <dfn id=dom-cva-checkvalidatity title=dom-cva-checkValidatity><code>checkValidity()</code></dfn>
   <dfn id=dom-cva-setcustomvalidity title=dom-cva-setCustomValidity><code>setCustomValidity()</code></dfn></p>
 
@@ -26663,7 +26663,7 @@
   <p>The <dfn id=application/x-www-form-urlencoded-encoding-algorithm><code title="">application/x-www-form-urlencoded</code> encoding
   algorithm</dfn> is as follows:</p>
 
-  <ol><li><p class=big-issue>...</li>
+  <ol><li><p class=XXX>...</li>
 
    <!-- During this step, the form data set is examined to ensure all
    the characters are representable in the submission character
@@ -26674,7 +26674,7 @@
   <p>The <dfn id=multipart/form-data-encoding-algorithm><code title="">multipart/form-data</code> encoding
   algorithm</dfn> is as follows:</p>
 
-  <ol><li><p class=big-issue>...</li>
+  <ol><li><p class=XXX>...</li>
 
    <!-- During this step, the form data set is examined to ensure all
    the characters are representable in the submission character
@@ -26685,7 +26685,7 @@
   <p>The <dfn id=text/plain-encoding-algorithm><code title="">text/plain</code> encoding
   algorithm</dfn> is as follows:</p>
 
-  <ol><li><p class=big-issue>...</li>
+  <ol><li><p class=XXX>...</li>
 
    <!-- During this step, the form data set is examined to ensure all
    the characters are representable in the submission character
@@ -26773,7 +26773,7 @@
   <p>The <dfn id=dom-details-open title=dom-details-open><code>open</code></dfn>
   attribute must <a href=#reflect>reflect</a> the <code title=attr-details-open><a href=#attr-details-open>open</a></code> content attribute.</p>
 
-  <p class=big-issue>Rendering will be described in the Rendering
+  <p class=XXX>Rendering will be described in the Rendering
   section in due course. Basically CSS :open and :closed match the
   element, it's a block-level element by default, and when it matches
   :closed it renders as if it had an XBL binding attached to it whose
@@ -26825,7 +26825,7 @@
   void <a href=#dom-datagrid-updatecellchanged title=dom-datagrid-updateCellChanged>updateCellChanged</a>(in <a href=#rowspecification>RowSpecification</a> row, in unsigned long column);
 };</pre>
    </dd>
-  </dl><p class=big-issue>One possible thing to be added is a way to
+  </dl><p class=XXX>One possible thing to be added is a way to
   detect when a row/selection has been deleted, activated, etc, by the
   user (delete key, enter key, etc).</p> <!-- XXXPA -->
 
@@ -26877,7 +26877,7 @@
   setting the <code title=attr-datagrid-disabled><a href=#attr-datagrid-disabled>disabled</a></code>
   attribute.</p>
 <!--XXXDND
-  <p class="big-issue">selection draggable [normative definitions are
+  <p class="XXX">selection draggable [normative definitions are
   in the interactive part below]</p>
 -->
 
@@ -27470,7 +27470,7 @@
 
     <p>The <code title=dom-provider-getCellClasses><a href=#dom-provider-getcellclasses>getCellClasses(<var title="">row</var>, <var title="">cell</var>, <var title="">classes</var>)</a></code> method must add no classes.</p>
 
-    <p class=big-issue><!-- select-provider-selection
+    <p class=XXX><!-- select-provider-selection
     XXX-->autoselect some rows when initialized, reflect the selection
     in the select, reflect the multiple attribute somehow.</p>
 
@@ -27595,7 +27595,7 @@
     definitions below</a>, treating the row's element as being the
     cell's element.</p>
 
-    <p class=big-issue id=generic-provider-selection>selection
+    <p class=XXX id=generic-provider-selection>selection
     handling?</p>
 
     <p>The data provider must call the <code><a href=#datagrid>datagrid</a></code>'s update
@@ -27755,7 +27755,7 @@
   fire a single <code title=event-load><a href=#event-load>load</a></code> event at itself,
   which doesn't bubble and cannot be canceled.</p>
 
-  <p class=big-issue>The end-tag parsing thing should be moved to
+  <p class=XXX>The end-tag parsing thing should be moved to
   the parsing section.</p>
 
   <p>The <code><a href=#datagrid>datagrid</a></code> must then populate itself using the
@@ -28001,7 +28001,7 @@
    the <code><a href=#htmlmenuelement>HTMLMenuElement</a></code> interface, i.e. a
    <code><a href=#menus>menu</a></code> element DOM node. (This element must then be
    interpreted as described in the section on context menus to obtain
-   the actual context menu to use.<!-- XXXX update once menu section
+   the actual context menu to use.<!-- XXX update once menu section
    works; with xrefs -->) If the method returns something that is not
    an <code><a href=#htmlmenuelement>HTMLMenuElement</a></code>, or if the method is not defined,
    then the row has no associated context menu. User agents may
@@ -28235,7 +28235,7 @@
   <code title=dom-datagrid-updateCellChanged><a href=#dom-datagrid-updatecellchanged>updateCellChanged()</a></code>
   method had been invoked, with the same row and column specified.</p>
 
-  <!-- XXXPA <p class="big-issue">define actions (performAction(), etc)</p> -->
+  <!-- XXXPA <p class="XXX">define actions (performAction(), etc)</p> -->
 
   <h5 id=the-selection><span class=secno>4.11.2.8 </span>The selection</h5>
 
@@ -28384,7 +28384,7 @@
 
   <p><em>This section only applies to interactive user agents.</em></p>
 
-  <p class="big-issue">define drag and drop in datagrids; selectiondraggable, etc.</p>
+  <p class="XXX">define drag and drop in datagrids; selectiondraggable, etc.</p>
 -->
 
 
@@ -28482,7 +28482,7 @@
 
   <div class=example>
 
-   <p class=big-issue>Need an example that shows an element that, if
+   <p class=XXX>Need an example that shows an element that, if
    double-clicked, invokes an action, but that also has a context
    menu, showing the various <code><a href=#the-command>command</a></code> attributes off, and
    that has a default command.</p>
@@ -28532,11 +28532,11 @@
   </dl><p class=note>Firing a synthetic <code title=event-click>click</code> event at the element does not cause
   any of the actions described above to happen.</p>
 
-  <p class=big-issue> should change all the above so it actually is
+  <p class=XXX> should change all the above so it actually is
   just triggered by a click event, then we could remove the shadowing
   click() method and rely on actual events. </p>
 
-  <p class=big-issue>Need to define the command="" attribute</p>
+  <p class=XXX>Need to define the command="" attribute</p>
 
   <p class=note><code><a href=#the-command>command</a></code> elements are not rendered
   unless they <a href=#menus title=menu>form part of a menu</a>.</p>
@@ -28774,7 +28774,7 @@
 
   <p><em>This section is non-normative.</em></p>
 
-  <p class=big-issue>...</p>
+  <p class=XXX>...</p>
 
 <!--
 
@@ -28932,7 +28932,7 @@
 
    <dd><a href=#ignore>Ignore</a> the node.</dd>
 
-  </dl><p class=big-issue>We should support <code><a href=#the-label-element>label</a></code> in the
+  </dl><p class=XXX>We should support <code><a href=#the-label-element>label</a></code> in the
   algorithm above -- just iterate through the contents like with
   <code><a href=#the-li-element>li</a></code>, to support <code><a href=#the-input-element>input</a></code> elements in
   <code><a href=#the-label-element>label</a></code> elements. Also, <code><a href=#the-optgroup-element>optgroup</a></code> elements
@@ -28975,7 +28975,7 @@
   does not, the default action must be for the user agent to show its
   default context menu, if it has one.</p>
 
-  <p class=big-issue>Context menus should inherit (so clicking on a
+  <p class=XXX>Context menus should inherit (so clicking on a
   span in a paragraph with a context menu should show the menu).</p>
 
   <p>If the element <em>does</em> have a context menu assigned, then
@@ -29097,7 +29097,7 @@
   </dl><p>Commands are represented by elements in the DOM. Any element that
   can define a command also implements the <code title=command-ro><a href=#command-ro>Command</a></code> interface:</p>
 
-  <p class=big-issue>Actually even better would be to just mix it
+  <p class=XXX>Actually even better would be to just mix it
   straight into those interfaces somehow.</p>
 
   <pre class=idl>[NoInterfaceObject] interface <dfn id=command-ro title=command-ro>Command</dfn> {<!--
@@ -29480,7 +29480,7 @@
 
   <p><em>This section is non-normative.</em></p>
 
-  <p class=big-issue>...examples...</p>
+  <p class=XXX>...examples...</p>
 
 
   <h4 id=the-datatemplate-element><span class=secno>4.12.2 </span>The <dfn><code>datatemplate</code></dfn> element</h4>
@@ -30175,9 +30175,9 @@
    <var title="">child node</var>, and <var title="">existing nodes
    lists</var> respectively.</li>
 
-  </ol><p class=big-issue>Define: <dfn id=evaluated-as-a-selector>evaluated as a selector</dfn></p>
+  </ol><p class=XXX>Define: <dfn id=evaluated-as-a-selector>evaluated as a selector</dfn></p>
 
-  <p class=big-issue>Define: <dfn id=text-expansion-algorithm-for-templates>text expansion algorithm for
+  <p class=XXX>Define: <dfn id=text-expansion-algorithm-for-templates>text expansion algorithm for
   templates</dfn></p> <!-- this is basically used for expanding
   nodeValue values -->
 
@@ -30220,7 +30220,7 @@
   common to a group of consecutive elements.</p>
 
 
-  <p class=big-issue>Allowing <code><a href=#the-div-element>div</a></code> elements to contain
+  <p class=XXX>Allowing <code><a href=#the-div-element>div</a></code> elements to contain
   phrasing content makes it easy for authors to abuse
   <code><a href=#the-div-element>div</a></code>, using it with the <code>class=""</code> attribute
   to the point of not having any other elements in the markup. This is
@@ -31351,7 +31351,7 @@
   <p>A node is said to be <dfn id=with-script>with script</dfn> if it is not
   <a href=#without-script>without script</a>.</p>
 
-  <p class=big-issue>If you can find a better pair of terms than
+  <p class=XXX>If you can find a better pair of terms than
   "with script" and "without script" let me know. The only things I
   can find that are less confusing are also way, way longer.</p>
 
@@ -31506,7 +31506,7 @@
 
   </dl><h4 id=security-exceptions><span class=secno>5.4.3 </span>Security exceptions</h4>
 
-  <p class=big-issue>Define <dfn id=security-exception>security exception</dfn>.</p>
+  <p class=XXX>Define <dfn id=security-exception>security exception</dfn>.</p>
 
 
 
@@ -31592,7 +31592,7 @@
 
   <h4 id=events><span class=secno>5.4.5 </span>Events</h4>
 
-  <p class=big-issue>We need to define how to handle events that are
+  <p class=XXX>We need to define how to handle events that are
   to be fired on a Document that is no longer the active document of
   its browsing context, and for Documents that have no browsing
   context. Do the events fire? Do the handlers in that document not
@@ -31664,7 +31664,7 @@
   reset the corresponding event handler attribute either.</p>
   <!-- http://software.hixie.ch/utilities/js/live-dom-viewer/?%3C!DOCTYPE%20html%3E%0A...%3Cbody%20onload%3D%22w(%27pass%27)%22%3E%0A%3Cscript%3Edocument.body.removeAttribute(%27onload%27)%3B%3C%2Fscript%3E -->
 
-  <p class=big-issue>How do we allow non-JS event handlers?</p>
+  <p class=XXX>How do we allow non-JS event handlers?</p>
 
   <p><dfn id=event-handler-dom-attributes>Event handler DOM attributes</dfn>, on setting, must set the
   corresponding event handler attribute to their new value, and on
@@ -31913,7 +31913,7 @@
 
   <h5 id=event-firing><span class=secno>5.4.5.2 </span>Event firing</h5>
 
-  <p class=big-issue>maybe this should be moved higher up
+  <p class=XXX>maybe this should be moved higher up
   (terminology? conformance? DOM?) Also, the whole terminology thing
   should be changed so that we don't define any specific events here,
   we only define 'simple event', 'progress event', 'mouse event', 'key
@@ -31954,7 +31954,7 @@
   element.</p>
 
   <p><dfn id=fire-a-show-event title="fire a show event">Firing a <code title=event-show>show</code> event</dfn> means <a href=#fire-a-simple-event title="fire a
-  simple event">firing a simple event called <code title=event-show>show</code></a>. <span class=big-issue>Actually this should fire an event that has
+  simple event">firing a simple event called <code title=event-show>show</code></a>. <span class=XXX>Actually this should fire an event that has
   modifier information (shift/ctrl etc), as well as having a pointer
   to the node on which the menu was fired, and with which the menu was
   associated (which could be an ancestor of the former).</span></p>
@@ -31971,14 +31971,14 @@
 
   <!-- XXX need to define the dispatching of DOMActivate -->
 
-  <p class=big-issue><dfn id=fire-a-progress-event title="fire a progress event">Firing a
+  <p class=XXX><dfn id=fire-a-progress-event title="fire a progress event">Firing a
   progress event called <var title="">e</var></dfn> means something
   that hasn't yet been defined, in the <a href=#refsPROGRESS>[PROGRESS]</a> spec.</p>
 
   <p>The default action of these event is to do nothing unless
   otherwise stated.</p>
 
-  <p class=big-issue>If you dispatch a custom "click" event at an
+  <p class=XXX>If you dispatch a custom "click" event at an
   element that would normally have default actions, should they get
   triggered? If so, we need to go through the entire spec and make
   sure that any default actions are defined in terms of <em>any</em>
@@ -32883,7 +32883,7 @@
 
   <p><em>This section is non-normative.</em></p>
 
-  <p class=big-issue>...</p>
+  <p class=XXX>...</p>
 
 
   <h4 id=appcache><span class=secno>5.7.2 </span>Application caches</h4>
@@ -33408,7 +33408,7 @@
   specification) to start the <dfn id=application-cache-update-process>application cache update
   process</dfn>, the user agent must run the following steps:</p>
 
-  <p class=big-issue>the event stuff needs to be more consistent --
+  <p class=XXX>the event stuff needs to be more consistent --
   something about showing every step of the ui or no steps or
   something; and we need to deal with showing ui for browsing contexts
   that open when an update is already in progress, and we may need to
@@ -34084,7 +34084,7 @@
   
    </li>
 
-  </ol><p class=big-issue>We can make the add() API more usable
+  </ol><p class=XXX>We can make the add() API more usable
   (i.e. make it possible to detect progress and distinguish success
   from errors without polling and timeouts) if we have the method
   return an object that is a target of Progress Events, much like the
@@ -34897,10 +34897,10 @@
   appropriate for the situation at hand. From the point of view of any
   script, these steps must occur atomically.</p>
 
-  <ol><li><p class=big-issue>pause for scripts -- but don't use the
+  <ol><li><p class=XXX>pause for scripts -- but don't use the
    "pause" definition since that involves not running script!</li>
 
-   <li><p class=big-issue>onbeforeunload, and if present set flag that we will kill document</li>
+   <li><p class=XXX>onbeforeunload, and if present set flag that we will kill document</li>
    <!--
    when we define onbeforeunload, then we have to say that the JS
    implementation of EventListener::handleEvent checks for that event,
@@ -34909,9 +34909,9 @@
    there isn't.
    -->
 
-   <li><p class=big-issue>onunload, and if present set flag that we will kill document</li>
+   <li><p class=XXX>onunload, and if present set flag that we will kill document</li>
 
-   <li><p class=big-issue>if flag is set: <a href=#discard-a-document title="discard a document">discard the <code>Document</code></a></li>
+   <li><p class=XXX>if flag is set: <a href=#discard-a-document title="discard a document">discard the <code>Document</code></a></li>
 
    <li>
 
@@ -35268,7 +35268,7 @@
    <code>Document</code> object than the <a href=#current-entry>current entry</a>
    then the user agent must run the following substeps:</p>
 
-    <ol><li class=big-issue>freeze any timers, intervals,
+    <ol><li class=XXX>freeze any timers, intervals,
      XMLHttpRequests, database transactions, etc</li>
 
      <li>The user agent must move any properties that have been added
@@ -35323,7 +35323,7 @@
      <a href=#list-of-added-properties>list of added properties</a> to browsing context's
      default view's <code><a href=#window>Window</a></code> object.</li>
 
-     <li class=big-issue>unfreeze any timers, intervals,
+     <li class=XXX>unfreeze any timers, intervals,
      XMLHttpRequests, database transactions, etc</li>
 
     </ol></li>
@@ -35358,26 +35358,26 @@
    <li><p>The <a href=#current-entry>current entry</a> is now the <i>specified
    entry</i>.</li>
 
-  </ol><p class=big-issue>how does the changing of the global attributes
+  </ol><p class=XXX>how does the changing of the global attributes
   affect .watch() when seen from other Windows?</p>
 
 
   <h4 id=closing-a-browsing-context><span class=secno>5.9.10 </span>Closing a browsing context</h4>
 
-  <p class=big-issue>Closing a browsing context and discarding it
+  <p class=XXX>Closing a browsing context and discarding it
   (vs closing it and keeping it around in memory).</p>
 
-  <p class=big-issue>when a browsing context is closed, all session
+  <p class=XXX>when a browsing context is closed, all session
   history entries' <code>Document</code> objects must be
   discarded.</p>
 
-  <p class=big-issue>When a user agent is to <dfn id=discard-a-document>discard a
+  <p class=XXX>When a user agent is to <dfn id=discard-a-document>discard a
   <code>Document</code></dfn>, any frozen timers, intervals,
   XMLHttpRequests, database transactions, etc, must be killed, and any
   MessagePorts owned by the Window object must be
   unentangled.</p>
 
-  <p class=big-issue>Also, <code title=event-unload>unload</code>
+  <p class=XXX>Also, <code title=event-unload>unload</code>
   events should fire.</p>
 
 
@@ -35789,7 +35789,7 @@
 
   <p><em>This section is non-normative.</em></p>
 
-  <p class=big-issue>...</p>
+  <p class=XXX>...</p>
 
 <!-- include an example that does something like the following to show
 you should never embed strings straight into the statement, even when you
@@ -35974,7 +35974,7 @@
 
     <p>The result is <i>the statement</i>.</p>
 
-    <p class=big-issue>Implementation feedback is requested on what
+    <p class=XXX>Implementation feedback is requested on what
     to do with arguments that are of types that are not supported by
     the underlying SQL backend. For example, SQLite doesn't support
     booleans, so what should the UA do if passed a boolean? The Gears
@@ -36130,7 +36130,7 @@
      because a row was being inserted and the value given for the
      primary key column duplicated the value of an existing row.
 
-  </table><p class=big-issue>We should define a more thorough list of
+  </table><p class=XXX>We should define a more thorough list of
   codes. Implementation feedback is requested to determine what codes
   are needed.</p>
 
@@ -37660,7 +37660,7 @@
 
   <p><em>This section is non-normative.</em></p>
 
-  <p class=big-issue>Would be nice to explain how these features
+  <p class=XXX>Would be nice to explain how these features
   work together.</p>
 
 
@@ -38209,7 +38209,7 @@
 
   <h4 id=textFieldSelection><span class=secno>6.6.2 </span>APIs for the text field selections</h4>
 
-  <p class=big-issue>When we define HTMLTextAreaElement and
+  <p class=XXX>When we define HTMLTextAreaElement and
   HTMLInputElement we will have to add the IDL given below to both of
   their IDLs.</p>
 
@@ -38637,7 +38637,7 @@
 
   <p><em>This section is non-normative.</em></p>
 
-  <p class=big-issue>It's also currently non-existent.</p>
+  <p class=XXX>It's also currently non-existent.</p>
 
 
   <h4 id=the-dragevent-and-datatransfer-interfaces><span class=secno>6.8.2 </span>The <code><a href=#dragevent>DragEvent</a></code> and <code><a href=#datatransfer>DataTransfer</a></code> interfaces</h4>
@@ -38651,7 +38651,7 @@
   void <a href=#dom-dragevent-initdrageventns title=dom-DragEvent-initDragEventNS>initDragEventNS</a>(in DOMString namespaceURIArg, in DOMString typeArg, in boolean canBubbleArg, in boolean cancelableArg, in AbstractView viewArg, in long detailArg, in <a href=#datatransfer>DataTransfer</a> dataTransferArg);
 };</pre>
 
-  <p class=big-issue>We should have modifier key information in here too
+  <p class=XXX>We should have modifier key information in here too
   (shift/ctrl, etc), like with mouse events and like with the context
   menu event.</p>
 
@@ -38900,7 +38900,7 @@
   be fired on the deepest node that is a common ancestor of all parts
   of the selection.</p>
 
-  <p class=big-issue>We should look into how browsers do other types
+  <p class=XXX>We should look into how browsers do other types
   (e.g. Firefox apparently also adds text/html for internal drag and
   drop of a selection).</p>
 
@@ -39412,7 +39412,7 @@
 
   <h3 id=undo><span class=secno>6.9 </span><dfn>Undo history</dfn></h3>
 
-  <p class=big-issue>There has got to be a better way of doing this, surely.</p>
+  <p class=XXX>There has got to be a better way of doing this, surely.</p>
 
   <p>The user agent must associate an <dfn id=undo-transaction-history>undo transaction
   history</dfn> with each <code><a href=#htmldocument>HTMLDocument</a></code> object.</p>
@@ -39453,7 +39453,7 @@
 
   <h4 id=the-undomanager-interface><span class=secno>6.9.1 </span>The <code><a href=#undomanager>UndoManager</a></code> interface</h4>
 
-  <div class=big-issue>
+  <div class=XXX>
 
    <p>This API sucks. Seriously. It's a terrible API. Really bad. I
    hate it. Here are the requirements:</p>
@@ -39548,7 +39548,7 @@
   position</a> must be removed (as if <code title=dom-UndoManager-clearRedo><a href=#dom-undomanager-clearredo>clearRedo()</a></code> had been
   called).</p>
 
-  <p class=big-issue>We could fire events when someone adds
+  <p class=XXX>We could fire events when someone adds
   something to the undo history -- one event per undo object entry
   before the position (or after, during redo addition), allowing the
   script to decide if that entry should remain or not. Or
@@ -39575,7 +39575,7 @@
   <a href=#dom-changes>DOM changes</a> entries or <a href=#undo-object>undo object</a>
   entries.</p>
 
-  <p class=big-issue>Another idea is to have a way for scripts to
+  <p class=XXX>Another idea is to have a way for scripts to
   say "startBatchingDOMChangesForUndo()" and after that the changes to
   the DOM go in as if the user had done them.</p>
 
@@ -40622,7 +40622,7 @@
 
   <p><em>This section is non-normative.</em></p>
 
-  <p class=big-issue>An introduction to the client-side and
+  <p class=XXX>An introduction to the client-side and
   server-side of using the direct connection APIs.</p>
 
 
@@ -40926,7 +40926,7 @@
     string "Upgrade: WebSocket", CRLF, the string
     "Connection: Upgrade", CRLF.</p>
 
-    <p class=big-issue>What if the response is a 401 asking for
+    <p class=XXX>What if the response is a 401 asking for
     credentials?</p>
 
    </li>
@@ -41252,7 +41252,7 @@
 
    <li><p>Send a 0xff byte to the server.</li>
 
-  </ol><p class=big-issue>People often request the ability to send binary
+  </ol><p class=XXX>People often request the ability to send binary
   blobs over this API; also, once the other postMessage() methods
   support it, we should look into allowing name/value pairs, arrays,
   and numbers using postMessage() instead of just strings and binary
@@ -41692,7 +41692,7 @@
 
   <h4 id=posting-structured-data><span class=secno>7.4.5 </span>Posting structured data</h4>
 
-  <p class=big-issue>People often request the ability to send
+  <p class=XXX>People often request the ability to send
   name/value pairs, arrays, and numbers using postMessage() instead of
   just strings.</p>
 
@@ -41705,7 +41705,7 @@
 
   <p><em>This section is non-normative.</em></p>
 
-  <p class=big-issue>An introduction to the channel and port
+  <p class=XXX>An introduction to the channel and port
   APIs.</p>
 
 
@@ -41881,7 +41881,7 @@
 
    <li><p>Add the event to the <a href=#port-message-queue>port message queue</a> of <var title="">target port</var>.</li>
 
-  </ol><p class=big-issue>People often request the ability to send
+  </ol><p class=XXX>People often request the ability to send
   name/value pairs, arrays, and numbers using postMessage() instead of
   just strings.</p>
 
@@ -45704,7 +45704,7 @@
     <p>Switch the <span>insertion mode</span> to "<a href=#the-before-head-insertion-mode title="insertion mode: before head">before head</a>", then
     reprocess the current token.</p>
 
-    <p class=big-issue>Should probably make end tags be ignored, so
+    <p class=XXX>Should probably make end tags be ignored, so
     that "</head><!-- --><html>" puts the comment before the
     root node (or should we?)</p>
 
@@ -45943,7 +45943,7 @@
     <p>Act as if an end tag token with the tag name "head" had
     been seen, and reprocess the current token.</p>
 
-    <p class=big-issue>In certain UAs, <a href="https://bugzilla.mozilla.org/attachment.cgi?id=180157&action=view">some
+    <p class=XXX>In certain UAs, <a href="https://bugzilla.mozilla.org/attachment.cgi?id=180157&action=view">some
     elements</a> don't trigger the "in body" mode straight away,
     but instead get put into the head. Do we want to copy
     that?</p>
@@ -46760,7 +46760,7 @@
 
 <!--XXX
     <div class="example">
-     <p class="big-issue">Need an example.</p>
+     <p class="XXX">Need an example.</p>
     </div>
 -->
 
@@ -47018,7 +47018,7 @@
     keywords here: (input field)" in the user's preferred
     language.</p>
 
-    <p class=big-issue> Then need to specify that if the form
+    <p class=XXX> Then need to specify that if the form
     submission causes just a single form control, whose name is
     "isindex", to be submitted, then we submit just the value part,
     not the "isindex=" part.  </p>
@@ -48532,7 +48532,7 @@
     <p><a href=#parse-error>Parse error</a>. Ignore the token.</p>
    </dd>
 
-  </dl><p class=big-issue>This doesn't handle UAs that don't support
+  </dl><p class=XXX>This doesn't handle UAs that don't support
   frames, or that do support frames but want to show the NOFRAMES
   content. Supporting the former is easy; supporting the latter is
   harder.</p>
@@ -48651,7 +48651,7 @@
 
   <!-- XXX make sure things "delay the load event" -->
 
-  <p class=big-issue>delaying the load event for things like image
+  <p class=XXX>delaying the load event for things like image
   loads allows for intranet port scans (even without
   javascript!). Should we really encode that into the spec?</p>
 
@@ -51407,7 +51407,7 @@
 
   -->
 
-  <p class=big-issue>This section will probably include details on
+  <p class=XXX>This section will probably include details on
   how to render DATAGRID (including <span id=datagridPseudos>its
   pseudo-elements</span>), drag-and-drop, etc, in a visual medium, in
   concert with CSS. Terms that need to be defined include: <dfn id=sizing-of-embedded-content>sizing
@@ -51460,12 +51460,12 @@
 -->
 
 
-  <p class=big-issue> must define letting the user "<dfn id=obtain-a-physical-form>obtain a
+  <p class=XXX> must define letting the user "<dfn id=obtain-a-physical-form>obtain a
   physical form</dfn> (or a representation of a physical form)" of a
   document (printing) and what this means for the UA, in particular
   creating a new view for the print media.</p>
 
-  <p class=big-issue>Must define that in CSS, tag and attribute
+  <p class=XXX>Must define that in CSS, tag and attribute
   names in HTML documents, and class names in quirks mode documents,
   are case-insensitive, as well as saying which attribute values must
   be compared case-insensitively.</p>
@@ -51473,7 +51473,7 @@
 
   <h3 id=rendering-and-the-dom><span class=secno>9.1 </span>Rendering and the DOM</h3>
 
-  <p class=big-issue>This section is wrong. mediaMode will end up on
+  <p class=XXX>This section is wrong. mediaMode will end up on
   Window, I think. All views implement Window.</p>
 
   <p>Any object implement the <code>AbstractView</code> interface must
@@ -51516,7 +51516,7 @@
 
   <h4 id=the-body-element-0><span class=secno>9.3.1 </span>The <code><a href=#the-body-element>body</a></code> element</h4>
 
-  <p class=big-issue>Need to define the content attributes in terms
+  <p class=XXX>Need to define the content attributes in terms
   of CSS or something.</p>
 
   <pre class=idl>[XXX] interface <a href=#htmldocument>HTMLDocument</a> {
@@ -51606,7 +51606,7 @@
   document</a>, then the element must be ignored (it represents
   nothing).</p>
 
-  <p>Otherwise, <span class=big-issue>define how the element works,
+  <p>Otherwise, <span class=XXX>define how the element works,
   if supported</span>.</p>
 
   <pre class=idl>[XXX] interface <a href=#htmldocument>HTMLDocument</a> {
@@ -51661,7 +51661,7 @@
 
   <h3 id=timers><span class=secno>10.4 </span>Timers</h3>
 
-  <p class=big-issue>This section is expected to be moved to its own
+  <p class=XXX>This section is expected to be moved to its own
   specification in due course. It needs a lot of work to actually make
   it into a semi-decent spec.</p>
 
@@ -51703,14 +51703,14 @@
 
   <p>Alternatively, <dfn title=""><code>setTimeout(<var title="">code</var>, <var title="">timeout</var>[, <var title="">language</var>])</code></dfn> may be used. This variant
   takes a string instead of a <code><a href=#timeouthandler>TimeoutHandler</a></code>
-  object. <span class=big-issue>define the actual requirements for
+  object. <span class=XXX>define the actual requirements for
   this method, as with the previous one.</span> That string must be
   parsed using the specified <var title="">language</var> (defaulting
   to ECMAScript if the third argument is omitted) and executed in the
   scope of the <a href=#browsing-context>browsing context</a> associated with the
   <code><a href=#window>Window</a></code> object on which the <code title=setTimeout>setTimeout()</code> method was invoked.</p>
 
-  <p class=big-issue>Need to define <var title="">language</var>
+  <p class=XXX>Need to define <var title="">language</var>
   values.</p>
 
   <p>The <dfn id=dom-windowtimers-setinterval title=dom-windowtimers-setInterval><code>setInterval(...)</code></dfn>
@@ -51736,19 +51736,18 @@
 
   <p><em>This section is non-normative.</em></p>
 
-  <p class=big-issue>List of elements</p>
+  <p class=XXX>List of elements</p>
 
-  <p class=big-issue>List of attributes</p>
+  <p class=XXX>List of attributes</p>
 
-  <p class=big-issue>List of interfaces</p>
+  <p class=XXX>List of interfaces</p>
 
-  <p class=big-issue>List of events</p>
+  <p class=XXX>List of events</p>
 
 
   <h2 class=no-num id=references>References</h2>
 
-  <p class=big-issue>This section will be written in a future
-  draft.<!--XXX--></p>
+  <p class=XXX>This section will be written in a future draft.</p>
 
   <!-- XXX check that #refsRFC([0-9]+) is always for [RFC\1] -->
 

Modified: source
===================================================================
--- source	2008-10-02 10:11:21 UTC (rev 2266)
+++ source	2008-10-02 10:16:19 UTC (rev 2267)
@@ -6,7 +6,7 @@
 
   <div id="stability"></div>
 
-  <p class="big-issue">Some of the more major known issues are marked
+  <p class="XXX">Some of the more major known issues are marked
   like this. There are many other issues that have been raised as
   well; the issues given in this document are not the only known
   issues! Also, firing of events needs to be unified (right now some
@@ -327,7 +327,7 @@
 
   <p class="example">This is an example.</p>
 
-  <p class="big-issue">This is an open issue.</p>
+  <p class="XXX">This is an open issue.</p>
 
   <p class="warning">This is a warning.</p>
 
@@ -920,7 +920,7 @@
 
   <h4>Features defined in other specifications</h4>
 
-  <p class="big-issue">this section will be removed at some point</p>
+  <p class="XXX">this section will be removed at some point</p>
 
   <p>Some elements are defined in terms of their DOM
   <dfn><code>textContent</code></dfn> attribute. This is an attribute
@@ -938,7 +938,7 @@
 
   <p>The term <dfn>activation behavior</dfn> is used as defined in the
   DOM3 Events specification. <a
-  href="#refsDOM3EVENTS">[DOM3EVENTS]</a> <span class="big-issue">At
+  href="#refsDOM3EVENTS">[DOM3EVENTS]</a> <span class="XXX">At
   the time of writing, DOM3 Events hadn't yet been updated to define
   that phrase.</span></p>
 
@@ -946,7 +946,7 @@
   style sheets are defined in the CSS object model specification. <a
   href="#refsCSSOM">[CSSOM]</a></p>
 
-  <p class="big-issue">See <a
+  <p class="XXX">See <a
   href="http://dev.w3.org/cvsweb/~checkout~/csswg/cssom/Overview.html?content-type=text/html;%20charset=utf-8">http://dev.w3.org/cvsweb/~checkout~/csswg/cssom/Overview.html?content-type=text/html;%20charset=utf-8</a></p>
   <!--XXX empty title attribute is equivalent to missing attribute for
   purposes of alternate style sheet processing -->
@@ -955,9 +955,9 @@
   <h4>Common conformance requirements for APIs exposed to
   JavaScript</h4>
 
-  <p class="big-issue">This section will eventually be removed in favour of WebIDL.</p>
+  <p class="XXX">This section will eventually be removed in favour of WebIDL.</p>
 
-  <p class="big-issue">A lot of arrays/lists/<span title="collections">collection</span>s
+  <p class="XXX">A lot of arrays/lists/<span title="collections">collection</span>s
   in this spec assume zero-based indexes but use the term "<var
   title="">index</var>th" liberally. We should define those to be
   zero-based and be clearer about this.</p>
@@ -965,19 +965,19 @@
   <p>Unless otherwise specified, if a DOM attribute that is a floating
   point number type (<code title="">float</code>) is assigned an
   Infinity or Not-a-Number value, a <code
-  class="big-issue">NOT_SUPPORTED_ERR</code> exception must be
+  class="XXX">NOT_SUPPORTED_ERR</code> exception must be
   raised.</p>
 
   <p>Unless otherwise specified, if a method with an argument that is a
   floating point number type (<code title="">float</code>) is passed
   an Infinity or Not-a-Number value, a <code
-  class="big-issue">NOT_SUPPORTED_ERR</code> exception must be
+  class="XXX">NOT_SUPPORTED_ERR</code> exception must be
   raised.</p>
 
   <!-- XXX DOMB -->
   <p>Unless otherwise specified, if a method is passed fewer
   arguments than is defined for that method in its IDL definition,
-  a <code class="big-issue">NOT_SUPPORTED_ERR</code> exception must be
+  a <code class="XXX">NOT_SUPPORTED_ERR</code> exception must be
   raised.</p>
 
   <!-- XXX DOMB -->
@@ -1033,7 +1033,7 @@
   <!-- XXX need to define how to handle U+000A LINE FEED and U+000D
   CARRIAGE RETURN in attributes (for HTML) -->
 
-  <p class="big-issue">Need to go through the whole spec and make sure
+  <p class="XXX">Need to go through the whole spec and make sure
   all the attribute values are clearly defined either in terms of
   microsyntaxes or in terms of other specs, or as "Text" or some
   such.</p>
@@ -1612,7 +1612,7 @@
 
   <h5 id="percentages-and-dimensions">Percentages and dimensions</h5>
 
-  <p class="big-issue"><dfn>valid positive non-zero integers</dfn>
+  <p class="XXX"><dfn>valid positive non-zero integers</dfn>
   <dfn>rules for parsing dimension values</dfn> (only used by
   height/width on img, embed, object — lengths in css pixels or
   percentages)</p>
@@ -1941,7 +1941,7 @@
 
   <h5>Specific moments in time</h5>
 
-  <p class="big-issue">This syntax is going to be tightened up and
+  <p class="XXX">This syntax is going to be tightened up and
   made almost exactly the same as the <span>valid UTC date and time
   string</span> syntax, with the exception of allowing time zones. In
   fact what we might do is allow time zones in general, use the same
@@ -2631,9 +2631,9 @@
   and a fraction of a second. <a
   href="#refsGREGORIAN">[GREGORIAN]</a></p>
 
-  <p class="big-issue">... <dfn>valid UTC date and time string</dfn></p>
+  <p class="XXX">... <dfn>valid UTC date and time string</dfn></p>
 
-  <p class="big-issue">... rules to <dfn>parse a UTC date and time
+  <p class="XXX">... rules to <dfn>parse a UTC date and time
   string</dfn></p>
 
 
@@ -2645,9 +2645,9 @@
   and a fraction of a second. <a
   href="#refsGREGORIAN">[GREGORIAN]</a></p>
 
-  <p class="big-issue">... <dfn>valid local date and time string</dfn></p>
+  <p class="XXX">... <dfn>valid local date and time string</dfn></p>
 
-  <p class="big-issue">... rules to <dfn>parse a local date and time
+  <p class="XXX">... rules to <dfn>parse a local date and time
   string</dfn></p>
 
 
@@ -2657,9 +2657,9 @@
   Gregorian date with no timezone information, consisting of a year, a
   month, and a day. <a href="#refsGREGORIAN">[GREGORIAN]</a></p>
 
-  <p class="big-issue">... <dfn>valid date string</dfn></p>
+  <p class="XXX">... <dfn>valid date string</dfn></p>
 
-  <p class="big-issue">... rules to <dfn>parse a date string</dfn></p>
+  <p class="XXX">... rules to <dfn>parse a date string</dfn></p>
 
 
   <h5>Months</h5>
@@ -2669,9 +2669,9 @@
   beyond a year and a month. <a
   href="#refsGREGORIAN">[GREGORIAN]</a></p>
 
-  <p class="big-issue">... <dfn>valid month string</dfn></p>
+  <p class="XXX">... <dfn>valid month string</dfn></p>
 
-  <p class="big-issue">... rules to <dfn>parse a month string</dfn></p>
+  <p class="XXX">... rules to <dfn>parse a month string</dfn></p>
 
 
   <h5>Weeks</h5>
@@ -2683,9 +2683,9 @@
 
   <!-- XXX ISO week information -->
 
-  <p class="big-issue">... <dfn>valid week string</dfn></p>
+  <p class="XXX">... <dfn>valid week string</dfn></p>
 
-  <p class="big-issue">... rules to <dfn>parse a week string</dfn></p>
+  <p class="XXX">... rules to <dfn>parse a week string</dfn></p>
 
 
   <h5>Times</h5>
@@ -2694,14 +2694,14 @@
   time with no timezone information, consisting of an hour, a minute,
   a second, and a fraction of a second.</p>
 
-  <p class="big-issue">... <dfn>valid time string</dfn></p>
+  <p class="XXX">... <dfn>valid time string</dfn></p>
 
-  <p class="big-issue">... rules to <dfn>parse a time string</dfn></p>
+  <p class="XXX">... rules to <dfn>parse a time string</dfn></p>
 
 
   <h5>Time offsets</h5>
 
-  <p class="big-issue"><dfn>valid time offset</dfn>, <dfn>rules for
+  <p class="XXX"><dfn>valid time offset</dfn>, <dfn>rules for
   parsing time offsets</dfn>, <dfn>time offset serialization
   rules</dfn>; probably in the format "5d4h3m2.1s" or similar, with
   all components being optional, and the last component's unit suffix
@@ -2856,7 +2856,7 @@
 
   <h4>Comma-separated tokens</h4>
 
-  <p class="big-issue">We should allow whitespace around commas, and
+  <p class="XXX">We should allow whitespace around commas, and
   leading/trailing whitespace.</p>
 
   <p>A <dfn>set of comma-separated tokens</dfn> is a set of zero or
@@ -4260,7 +4260,7 @@
 
   </table>
 
-  <p class="big-issue">I'd like to add types like MPEG, AVI, Flash,
+  <p class="XXX">I'd like to add types like MPEG, AVI, Flash,
   Java, etc, to the above table.</p>
 
   <p>User agents may support further types if desired, by implicitly
@@ -4493,7 +4493,7 @@
 
    </li>
 
-   <li><p class="big-issue">If, before the next ">", you find two
+   <li><p class="XXX">If, before the next ">", you find two
    xmlns* attributes with http://www.w3.org/1999/02/22-rdf-syntax-ns#
    and http://purl.org/rss/1.0/ as the namespaces, then the sniffed
    type of the resource is "application/rss+xml", abort these
@@ -4903,7 +4903,7 @@
 
   <!-- see also http://ln.hixie.ch/?start=1161042744&count=1 -->
 
-  <p class="big-issue">We may want to add <code>add()</code> and
+  <p class="XXX">We may want to add <code>add()</code> and
   <code>remove()</code> methods here too because IE implements
   HTMLSelectElement and HTMLOptionsCollection on the same object, and
   so people use them almost interchangeably in the wild.</p>
@@ -5065,7 +5065,7 @@
   values from names, one for setting names to certain values, and one
   for deleting names.</p>
 
-  <p class="big-issue">The names of the methods on this interface are
+  <p class="XXX">The names of the methods on this interface are
   temporary and will be fixed when the Web IDL / "Language Bindings
   for DOM Specifications" spec is ready to handle this case.</p>
 
@@ -5139,7 +5139,7 @@
 
   <p><em>This section is non-normative.</em></p>
 
-  <p class="big-issue">An introduction to marking up a document.</p>
+  <p class="XXX">An introduction to marking up a document.</p>
 
 
   <h3>Documents</h3>
@@ -5389,7 +5389,7 @@
   case it must instead return the literal string "<code
   title="">BackCompat</code>".</p>
 
-  <div class="big-issue">
+  <div class="XXX">
 
    <p>As far as parsing goes, the quirks I know of are:</p>
 
@@ -6624,7 +6624,7 @@
   all cross-references. Some of them refer specifically to the
   activation behavior stuff. -->
 
-  <p class="big-issue">Parts of this section should eventually be
+  <p class="XXX">Parts of this section should eventually be
   moved to DOM3 Events.</p> <!-- but see comment above -->
 
 <!--
@@ -7011,12 +7011,12 @@
 
    </li>
 
-   <li><p class="big-issue">onbeforeunload, onunload, reset timers, empty event queue, kill any pending transactions, XMLHttpRequests, etc</p></li>
+   <li><p class="XXX">onbeforeunload, onunload, reset timers, empty event queue, kill any pending transactions, XMLHttpRequests, etc</p></li>
    <!-- http://software.hixie.ch/utilities/js/live-dom-viewer/?%3C!DOCTYPE%20html%3E...%3Ciframe%20src%3D%22document%22%3E%3C%2Fiframe%3E%0A%3Cscript%3Eonload%20%3D%20function%20()%20{%20f%20%3D%20document.getElementsByTagName(%27iframe%27)[0]%3B%20d%20%3D%20f.contentDocument%3B%20}%3C%2Fscript%3E%0A%3Cinput%20type%3Dbutton%20onclick%3D%22w(d.documentElement.innerHTML)%22%20value%3D%22dump%22%3E%0A%3Cinput%20type%3Dbutton%20onclick%3D%22d.body.bgColor%3D%27red%27%22%20value%3D%22color%22%3E%0A%3Cinput%20type%3Dbutton%20onclick%3D%22f.style.border%3D%27lime%20solid%27%22%20value%3D%22color%20frame%22%3E%0A%3Cinput%20type%3Dbutton%20onclick%3D%22d.open()%3B%20d.write(%27%3Cp%3Etest%3C%2Fp%3E%27)%3B%20d.close()%22%20value%3D%22replace%22%3E%0A%3Cinput%20type%3Dbutton%20onclick%3D%22d.open()%3B%20d.write(%27%3Cp%3E%3Cscript%3Ei%20%3D%200%3B%20setInterval(%26quot%3Bparent.w(i%2B%2B)%26quot%3B%2C%20500)%3C%2Fscript%3E%3C%2Fp%3E%27)%3B%20d.close()%22%20value%3D%22replace%20with%20timer%22%3E%0A -->
 
    <li><p>If the document has an <span>active parser</span><!--XXX
    xref-->, then stop that parser, and throw away any pending content
-   in the input stream. <span class="big-issue">what about if it
+   in the input stream. <span class="XXX">what about if it
    doesn't, because it's either like a text/plain, or Atom, or PDF, or
    XHTML, or image document, or something?</span></p></li><!-- XXX see
    also innerHTML in HTML -->
@@ -7205,7 +7205,7 @@
 
     <p>If the document has an <span>active parser</span><!--XXX
     xref-->, then stop that parser, and throw away any pending content
-    in the input stream. <span class="big-issue">what about if it
+    in the input stream. <span class="XXX">what about if it
     doesn't, because it's either like a text/plain, or Atom, or PDF,
     or XHTML, or image document, or something?</span></p><!-- XXX see
     also document.open() -->
@@ -8663,7 +8663,7 @@
 
     <ol>
 
-     <li class="big-issue">...</li>
+     <li class="XXX">...</li>
 
     </ol>
 
@@ -9081,7 +9081,7 @@
   getting, and forward the new value to that same attribute on
   setting.</p>
 
-  <!-- <p class="big-issue">Need more here - defining preferred
+  <!-- <p class="XXX">Need more here - defining preferred
   stylesheets, alternative stylesheets, persistent stylesheets, ordering
   of stylesheets, dynamic additions/removals, how it maps to
   .styleSheets, HTTP Link: headers, and the stuff about the alternative
@@ -9398,7 +9398,7 @@
      scripts that will execute when the document has finished
      parsing</span>.
  
-     <span class="big-issue">This isn't compatible with IE for inline
+     <span class="XXX">This isn't compatible with IE for inline
      deferred scripts, but then what IE does is pretty hard to pin down
      exactly. Do we want to keep this like it is? Be more compatible?</span>
      <!--XXX  
@@ -9617,7 +9617,7 @@
         of any metadata given by the file's <span
         title="Content-Type">Content-Type metadata</span>.</p>
 
-        <p class="big-issue">This means that a UTF-16 document will
+        <p class="XXX">This means that a UTF-16 document will
         always assume external scripts are UTF-16...? This applies,
         e.g., to document's created using createDocument()... It also
         means changing document.charSet will affect the character
@@ -11945,7 +11945,7 @@
    title="dom-click">click()</code> method call was the reason for the
    event being dispatched), and the <code>a</code> element's <code
    title="attr-hyperlink-target">target</code> attribute is <span
-   class="big-issue">...</span> then raise an
+   class="XXX">...</span> then raise an
    <code>INVALID_ACCESS_ERR</code> exception and abort these
    steps.</p></li>
 
@@ -12457,7 +12457,7 @@
   part of the document that has been highlighted due to its likely
   relevance to the user's current activity.</p>
 
-  <p class="big-issue">The rendering section will eventually suggest
+  <p class="XXX">The rendering section will eventually suggest
   that user agents provide a way to let users jump between
   <code>mark</code> elements. Suggested rendering is a neon yellow
   background highlight, though UAs maybe should allow this to be
@@ -12877,7 +12877,7 @@
 
   </div>
 
-  <p class="big-issue">These APIs may be suboptimal. Comments on
+  <p class="XXX">These APIs may be suboptimal. Comments on
   making them more useful to JS authors are welcome. The primary use
   cases for these elements are for marking up publication dates
   e.g. in blog entries, and for marking event dates in hCalendar
@@ -13057,7 +13057,7 @@
   attributes must return zero. The value parsed from the
   <code>textContent</code> never affects the DOM values.</p>
 
-  <p class="big-issue">Would be cool to have the <code
+  <p class="XXX">Would be cool to have the <code
   title="dom-progress-value">value</code> DOM attribute update the
   <code>textContent</code> in-line...</p>
 
@@ -13458,7 +13458,7 @@
   attributes must return zero. The value parsed from the
   <code>textContent</code> never affects the DOM values.</p>
 
-  <p class="big-issue">Would be cool to have the <code
+  <p class="XXX">Would be cool to have the <code
   title="dom-meter-value">value</code> DOM attribute update the
   <code>textContent</code> in-line...</p>
 
@@ -14056,7 +14056,7 @@
 
   <h4>Usage summary</h4>
 
-  <p class="big-issue">We need to summarize the various elements, in
+  <p class="XXX">We need to summarize the various elements, in
   particular to distinguish b/i/em/strong/var/q/mark/cite.</p>
 
   <!-- XXX when you do this, also reorder the elements in this section
@@ -14627,7 +14627,7 @@
   attribute's value are described <a href="#alt">in the next
   section</a>.</p>
 
-  <p class="big-issue">There has been some suggestion that the <code
+  <p class="XXX">There has been some suggestion that the <code
   title="">longdesc</code> attribute from HTML4, or some other
   mechanism that is more powerful than <code title="">alt=""</code>,
   should be included. This has not yet been considered.</p>
@@ -16218,7 +16218,7 @@
 
   </ul>
 
-  <p class="big-issue">Parts of the above might get moved into the
+  <p class="XXX">Parts of the above might get moved into the
   rendering section at some point.</p>
 
   <p>If the attribute is not specified, or if the <span>origin</span>
@@ -16274,7 +16274,7 @@
   that could act as fallback content.)</p>
 
   <p>The content model of <code>iframe</code> elements is text, except
-  that the text must be such that <span class="big-issue">... anyone
+  that the text must be such that <span class="XXX">... anyone
   have any bright ideas?</span></p>
   <!--XXX
     Gotta handle <script> elements inside <iframe>s that screw around with the DOM on the fly, or that use document.write().
@@ -16423,7 +16423,7 @@
     components that end with the four character string "<code
     title="">.swf</code>".</p>
 
-    <p class="big-issue">It would be better if browsers didn't do
+    <p class="XXX">It would be better if browsers didn't do
     extension sniffing like this, and only based their decision on the
     actual contents of the resource. Couldn't we just apply the
     <span>sniffed type of a resource</span> steps?</p>
@@ -16734,7 +16734,7 @@
         to the value of this attribute; otherwise, the <span>browsing
         context name</span> must be set to the empty string.</p>
 
-        <p class="big-issue">navigation might end up treating it as
+        <p class="XXX">navigation might end up treating it as
         something else, because it can do sniffing. how should we
         handle that?</p>
 
@@ -17235,7 +17235,7 @@
   provided to easily allow the user to obtain a full-screen playback
   mode.</p>
 
-  <p class="big-issue">The spec does not currently define the
+  <p class="XXX">The spec does not currently define the
   interaction of the "controls" attribute with the "height" and
   "width" attributes. This will likely be defined in the rendering
   section based on implementation experience. So far, browsers seem to
@@ -17249,7 +17249,7 @@
   <p>User agents may support any video and audio codecs and container
   formats.</p>
 
-  <p class="big-issue">It would be helpful for interoperability if all
+  <p class="XXX">It would be helpful for interoperability if all
   browsers could support the same codecs. However, there are no known
   codecs that satisfy all the current players: we need a codec that is
   known to not require per-unit or per-distributor licensing, that is
@@ -18241,7 +18241,7 @@
 
       <ol>
 
-       <li class="big-issue">Should we fire a 'warning' event? Set the
+       <li class="XXX">Should we fire a 'warning' event? Set the
        'error' flag to 'MEDIA_ERR_SUBOPTIMAL' or something?</li>
 
       </ol>
@@ -19621,7 +19621,7 @@
 
   <h5>Security and privacy considerations</h5>
 
-  <p class="big-issue">Talk about making sure interactive media files
+  <p class="XXX">Talk about making sure interactive media files
   (e.g. SVG) don't have access to the container DOM (XSS potential);
   talk about not exposing any sensitive data like metadata from tracks
   in the media files (intranet snooping risk)</p>
@@ -21522,7 +21522,7 @@
    characters</span> in <var title="">text</var> with U+0020 SPACE
    characters.</p></li>
 
-   <li><p>Form a <em class="big-issue">whatever CSS ends up calling
+   <li><p>Form a <em class="XXX">whatever CSS ends up calling
    vertical line boxes and inline boxes</em> containing the text <var
    title="">text</var>, with all the properties at their initial
    values except the 'font' property of the inline box set to <var
@@ -21534,7 +21534,7 @@
    final words - ->
 
    <li><p>If the <var title="">maxHeight</var> argument was specified
-   and the hypothetical height of the <em class="big-issue">box</em>
+   and the hypothetical height of the <em class="XXX">box</em>
    in the hypothetical line box is greater than <var
    title="">maxHeight</var> CSS pixels, then change <var
    title="">font</var> to have a more condensed font (if one is
@@ -21545,7 +21545,7 @@
    <li>
 
     <p>Let the <var title="">anchor point</var> be a point on the <em
-    class="big-issue">inline box</var>, determined by the <code
+    class="XXX">inline box</var>, determined by the <code
     title="dom-context-2d-textAlign">textAlign</code>, as follows:</p>
 
     <p>Vertical position:</p>
@@ -21565,7 +21565,7 @@
      <code>canvas</code> element is 'rtl'</dt>
 
      <dd>Let the <var title="">anchor point</var>'s vertical
-     position be the top edge of the <em class="big-issue">inline
+     position be the top edge of the <em class="XXX">inline
      box</em>.</dd>
 
      <dt> If <code
@@ -21581,7 +21581,7 @@
      <code>canvas</code> element is 'rtl'</dt>
 
      <dd>Let the <var title="">anchor point</var>'s vertical
-     position be the bottom edge of the <em class="big-issue">inline
+     position be the bottom edge of the <em class="XXX">inline
      box</em>.</dd>
 
 
@@ -21591,13 +21591,13 @@
 
      <dd>Let the <var title="">anchor point</var>'s vertical position
      be half way between the top and bottom edges of the <em
-     class="big-issue">inline box</em>.</dd>
+     class="XXX">inline box</em>.</dd>
 
     </dl>
 
     <p>Let the horizontal position be half way between the left and
     right edges of the em box of the first available font of the <em
-    class="big-issue">inline box</em>.</p>
+    class="XXX">inline box</em>.</p>
 
    </li>
 
@@ -21874,7 +21874,7 @@
   rounding mode.  <a href="#refsECMA262">[ECMA262]</a> <a
   href="#refsIEEE754r">[IEEE754R]</a></p>
 
-  <p class="big-issue">The above is not intended to cause these
+  <p class="XXX">The above is not intended to cause these
   methods to get any unusual behaviour, it's just supposed to be the
   normal behaviour for passing values to a method expecting an <code
   title="">octet</code> type.</p>
@@ -22184,7 +22184,7 @@
 <!--
   <h5 id="3d">The 3D context</h5>
 
-  <p class="big-issue">Well, one day.</p>
+  <p class="XXX">Well, one day.</p>
 -->
 
 
@@ -22547,7 +22547,7 @@
    title="dom-click">click()</code> method call was the reason for the
    event being dispatched), and the <code>area</code> element's <code
    title="attr-area-target">target</code> attribute is <span
-   class="big-issue">...</span> then raise an
+   class="XXX">...</span> then raise an
    <code>INVALID_ACCESS_ERR</code> exception.</li>
 
    <li>Otherwise, the user agent must <span title="following
@@ -22988,7 +22988,7 @@
 
   <p><em>This section is non-normative.</em></p>
 
-  <p class="big-issue">...examples, how to write tables accessibly, a
+  <p class="XXX">...examples, how to write tables accessibly, a
   brief mention of the table model, etc...</p>
 
 
@@ -23034,7 +23034,7 @@
   <p>The <code>table</code> element represents data with more than one
   dimension (a <span title="concept-table">table</span>).</p>
 
-  <p class="big-issue">we need some editorial text on how layout
+  <p class="XXX">we need some editorial text on how layout
   tables are bad practice and non-conforming</p>
 
   <p>The children of a <code>table</code> element must be, in
@@ -26415,7 +26415,7 @@
   title="attr-input-type-hidden">Hidden</span> state, the rules in
   this section apply.</p>
 
-  <p class="big-issue">...</p>
+  <p class="XXX">...</p>
 
   <p><strong>Constraint validation:</strong> If an <code>input</code>
   element's <code title="attr-input-type">type</code> attribute is in
@@ -27867,7 +27867,7 @@
   title="attr-input-type-file">File</span> state, the rules in this
   section apply.</p>
 
-  <p class="big-issue">...</p>
+  <p class="XXX">...</p>
 
   <p>The <dfn title="attr-input-accept"><code>accept</code></dfn>
   attribute may be specified to provide user agents with a hint of
@@ -27903,7 +27903,7 @@
 
   <!-- XXX the selected file(s) must either have the given types or be of the given category -->
 
-  <p class="big-issue">... list of <dfn title="concept-input-type-file-selected">selected files</dfn></p>
+  <p class="XXX">... list of <dfn title="concept-input-type-file-selected">selected files</dfn></p>
 
 
 
@@ -27914,7 +27914,7 @@
   title="attr-input-type-submit">Submit Button</span> state, the rules
   in this section apply.</p>
 
-  <p class="big-issue">...</p>
+  <p class="XXX">...</p>
 
 <!--XXX
 rel="" on submit buttons?
@@ -27929,13 +27929,13 @@
   title="attr-input-type-image">Image Button</span> state, the rules
   in this section apply.</p>
 
-  <p class="big-issue">...</p>
+  <p class="XXX">...</p>
 
-  <p class="big-issue">... <dfn title="attr-input-alt"><code>alt</code></dfn></p>
+  <p class="XXX">... <dfn title="attr-input-alt"><code>alt</code></dfn></p>
 
-  <p class="big-issue">... <dfn title="attr-input-src"><code>src</code></dfn></p>
+  <p class="XXX">... <dfn title="attr-input-src"><code>src</code></dfn></p>
 
-  <p class="big-issue">... image: <dfn title="concept-input-type-image-coordinate">selected coordinate</dfn></p>
+  <p class="XXX">... image: <dfn title="concept-input-type-image-coordinate">selected coordinate</dfn></p>
 
 
 
@@ -27946,7 +27946,7 @@
   title="attr-input-type-reset">Reset Button</span> state, the rules
   in this section apply.</p>
 
-  <p class="big-issue">...</p>
+  <p class="XXX">...</p>
 
   <p><strong>Constraint validation:</strong> If an <code>input</code>
   element's <code title="attr-input-type">type</code> attribute is in
@@ -27962,7 +27962,7 @@
   title="attr-input-type-button">Button</span> state, the rules in
   this section apply.</p>
 
-  <p class="big-issue">...</p>
+  <p class="XXX">...</p>
 
   <p><strong>Constraint validation:</strong> If an <code>input</code>
   element's <code title="attr-input-type">type</code> attribute is in
@@ -28065,7 +28065,7 @@
 
   <h6>The <code title="attr-input-list">list</code> attribute</h6>
 
-  <p class="big-issue">... <dfn title="attr-input-list"><code>list</code></dfn></p>
+  <p class="XXX">... <dfn title="attr-input-list"><code>list</code></dfn></p>
 
 
 
@@ -28084,13 +28084,13 @@
 
   <h6>The <code title="attr-input-size">size</code> attribute</h6>
 
-  <p class="big-issue">... <dfn title="attr-input-size"><code>size</code></dfn></p>
+  <p class="XXX">... <dfn title="attr-input-size"><code>size</code></dfn></p>
 
 
 
   <h6>The <code title="attr-input-required">required</code> attribute</h6>
 
-  <p class="big-issue">... <dfn title="attr-input-required"><code>required</code></dfn></p>
+  <p class="XXX">... <dfn title="attr-input-required"><code>required</code></dfn></p>
 
 
 
@@ -28135,7 +28135,7 @@
 
   <h6>The <code title="attr-input-pattern">pattern</code> attribute</h6>
 
-  <p class="big-issue">... <dfn title="attr-input-pattern"><code>pattern</code></dfn></p>
+  <p class="XXX">... <dfn title="attr-input-pattern"><code>pattern</code></dfn></p>
 
 
 
@@ -28491,8 +28491,8 @@
 
   <hr>
 
-  <p class="big-issue">... <dfn title="dom-input-list"><code>list</code></dfn></p>
-  <p class="big-issue">... <dfn title="dom-input-selectedOption"><code>selectedOption</code></dfn></p>
+  <p class="XXX">... <dfn title="dom-input-list"><code>list</code></dfn></p>
+  <p class="XXX">... <dfn title="dom-input-selectedOption"><code>selectedOption</code></dfn></p>
 
 
 
@@ -28544,7 +28544,7 @@
    </dd> 
   </dl>
 
-  <p class="big-issue">...</p>
+  <p class="XXX">...</p>
 
   <p>The <code title="attr-fae-form">form</code> attribute is used to
   explicitly associate the <code>button</code> element with its
@@ -28617,7 +28617,7 @@
    </dd> 
   </dl>
 
-  <p class="big-issue">...</p>
+  <p class="XXX">...</p>
 
   <p>The <code title="attr-fae-form">form</code> attribute is used to
   explicitly associate the <code>select</code> element with its
@@ -28658,7 +28658,7 @@
    </dd> 
   </dl>
 
-  <p class="big-issue">...</p>
+  <p class="XXX">...</p>
 
   <p><strong>Constraint validation:</strong> If an element has a
   <code>datalist</code> element ancestor, it is <span>barred from
@@ -28686,7 +28686,7 @@
    </dd> 
   </dl>
 
-  <p class="big-issue">...</p>
+  <p class="XXX">...</p>
 
 
   <h4>The <dfn><code>option</code></dfn> element</h4>
@@ -28724,13 +28724,13 @@
    </dd> 
   </dl>
 
-  <p class="big-issue">...</p>
+  <p class="XXX">...</p>
 
-  <p class="big-issue">... <dfn title="concept-option-selected">selected</dfn></p>
+  <p class="XXX">... <dfn title="concept-option-selected">selected</dfn></p>
 
-  <p class="big-issue">... <dfn title="concept-option-value">value</dfn></p>
+  <p class="XXX">... <dfn title="concept-option-value">value</dfn></p>
 
-  <p class="big-issue">
+  <p class="XXX">
    <dfn title="dom-option"><code>Option()</code></dfn>
    <dfn title="dom-option-n"><code>Option(<var title="">name</var>)</code></dfn>
    <dfn title="dom-option-nv"><code>Option(<var title="">name</var>, <var title="">value</var>)</code></dfn>
@@ -28796,7 +28796,7 @@
 
   <!-- XXX add selectionStart and company -->
 
-  <p class="big-issue">...</p>
+  <p class="XXX">...</p>
 
   <p>The <code title="attr-fae-form">form</code> attribute is used to
   explicitly associate the <code>textarea</code> element with its
@@ -28856,7 +28856,7 @@
    </dd> 
   </dl>
 
-  <p class="big-issue">...</p>
+  <p class="XXX">...</p>
 
   <p>The <code title="attr-fae-form">form</code> attribute is used to
   explicitly associate the <code>output</code> element with its
@@ -28985,9 +28985,9 @@
 
   <h5>Naming form controls</h5>
 
-  <p class="big-issue">... <dfn title="attr-fe-name">name</dfn> content attribute</p>
+  <p class="XXX">... <dfn title="attr-fe-name">name</dfn> content attribute</p>
 
-  <p class="big-issue">... <dfn title="dom-fe-name">name</dfn> DOM attribute</p>
+  <p class="XXX">... <dfn title="dom-fe-name">name</dfn> DOM attribute</p>
 
   <p><strong>Constraint validation:</strong> If an element does not
   have a <code title="attr-fe-name">name</code> attribute specified,
@@ -28999,13 +28999,13 @@
 
   <h5>Enabling and disabling form controls</h5>
 
-  <p class="big-issue">... <dfn title="concept-fe-disabled">disabled</dfn></p>
+  <p class="XXX">... <dfn title="concept-fe-disabled">disabled</dfn></p>
   <!-- XXX remember to check for a fieldset ancestor that has its
   disabled attribute set, and always be disabled if you find one -->
 
-  <p class="big-issue">... <dfn title="attr-fe-disabled">disabled</dfn> content attribute</p>
+  <p class="XXX">... <dfn title="attr-fe-disabled">disabled</dfn> content attribute</p>
 
-  <p class="big-issue">... <dfn title="dom-fe-disabled">disabled</dfn> DOM attribute</p>
+  <p class="XXX">... <dfn title="dom-fe-disabled">disabled</dfn> DOM attribute</p>
 
   <p><strong>Constraint validation:</strong> If an element is <span
   title="concept-fe-disabled">disabled</span>, it is <span>barred from
@@ -29015,8 +29015,8 @@
 
   <h5>A form control's value</h5>
 
-  <p class="big-issue">... <dfn title="concept-fe-value">value</dfn></p>
-  <p class="big-issue">... <dfn title="concept-fe-checked">checkedness</dfn></p>
+  <p class="XXX">... <dfn title="concept-fe-value">value</dfn></p>
+  <p class="XXX">... <dfn title="concept-fe-checked">checkedness</dfn></p>
   <!-- XXX autocomplete: define somewhere that the value may be set from a stored value -->
 
 
@@ -29068,30 +29068,30 @@
 
   <h4><dfn>Attributes for form submission</dfn></h4>
 
-  <p class="big-issue">... <dfn title="attr-fs-action">action</dfn> content attribute</p>
+  <p class="XXX">... <dfn title="attr-fs-action">action</dfn> content attribute</p>
 
-  <p class="big-issue">... <dfn title="dom-fs-action">action</dfn> DOM attribute</p>
+  <p class="XXX">... <dfn title="dom-fs-action">action</dfn> DOM attribute</p>
 
-  <p class="big-issue">... <dfn title="concept-fs-action">action</dfn> if present else form's else default</p>
+  <p class="XXX">... <dfn title="concept-fs-action">action</dfn> if present else form's else default</p>
   <!-- XXX mozilla bug 297761 -->
 
-  <p class="big-issue">... <dfn title="attr-fs-method">method</dfn> content attribute</p>
+  <p class="XXX">... <dfn title="attr-fs-method">method</dfn> content attribute</p>
 
-  <p class="big-issue">... <dfn title="dom-fs-method">method</dfn> DOM attribute</p>
+  <p class="XXX">... <dfn title="dom-fs-method">method</dfn> DOM attribute</p>
 
-  <p class="big-issue">... <dfn title="concept-fs-method">method</dfn> if present else form's else default</p>
+  <p class="XXX">... <dfn title="concept-fs-method">method</dfn> if present else form's else default</p>
 
-  <p class="big-issue">... <dfn title="attr-fs-enctype">enctype</dfn> content attribute</p>
+  <p class="XXX">... <dfn title="attr-fs-enctype">enctype</dfn> content attribute</p>
 
-  <p class="big-issue">... <dfn title="dom-fs-enctype">enctype</dfn> DOM attribute</p>
+  <p class="XXX">... <dfn title="dom-fs-enctype">enctype</dfn> DOM attribute</p>
 
-  <p class="big-issue">... <dfn title="concept-fs-enctype">enctype</dfn> if present else form's else default</p>
+  <p class="XXX">... <dfn title="concept-fs-enctype">enctype</dfn> if present else form's else default</p>
 
-  <p class="big-issue">... <dfn title="attr-fs-target">target</dfn> content attribute</p>
+  <p class="XXX">... <dfn title="attr-fs-target">target</dfn> content attribute</p>
 
-  <p class="big-issue">... <dfn title="dom-fs-target">target</dfn> DOM attribute</p>
+  <p class="XXX">... <dfn title="dom-fs-target">target</dfn> DOM attribute</p>
 
-  <p class="big-issue">... <dfn title="concept-fs-target">target</dfn> if present else form's else base target else default</p> <!-- c.f. hyperlink following -->
+  <p class="XXX">... <dfn title="concept-fs-target">target</dfn> if present else form's else base target else default</p> <!-- c.f. hyperlink following -->
 
   <p>Attributes for form submission can be specified both on
   <code>form</code> elements and on elements that represent buttons
@@ -29115,20 +29115,20 @@
   constraint validation</span> if it is an <code>output</code> or
   <code>fieldset</code> element.)</p>
 
-  <p class="big-issue">An element <dfn
+  <p class="XXX">An element <dfn
   title="concept-fv-valid">satisfies its constraints</dfn> if ...</p>
 
-  <p class="big-issue">... <dfn>suffering from a type
+  <p class="XXX">... <dfn>suffering from a type
   mismatch</dfn></p>
 
-  <p class="big-issue">... <dfn>suffering from being too
+  <p class="XXX">... <dfn>suffering from being too
   long</dfn></p>
 
-  <p class="big-issue">... <dfn>suffering from an underflow</dfn></p>
+  <p class="XXX">... <dfn>suffering from an underflow</dfn></p>
 
-  <p class="big-issue">... <dfn>suffering from an overflow</dfn></p>
+  <p class="XXX">... <dfn>suffering from an overflow</dfn></p>
 
-  <p class="big-issue">... <dfn>suffering from a step
+  <p class="XXX">... <dfn>suffering from a step
   mismatch</dfn></p>
 
 
@@ -29251,7 +29251,7 @@
   conditions are <span title="barred from constraint
   validation">barring it from constraint validation</span>).</p>
 
-  <p class="big-issue"> <dfn
+  <p class="XXX"> <dfn
   title="dom-cva-validity"><code>validity</code></dfn> <dfn
   title="dom-cva-validationMessage"><code>validationMessage</code></dfn>
   <dfn
@@ -29850,7 +29850,7 @@
 
   <ol>
 
-   <li><p class="big-issue">...</p></li>
+   <li><p class="XXX">...</p></li>
 
    <!-- During this step, the form data set is examined to ensure all
    the characters are representable in the submission character
@@ -29866,7 +29866,7 @@
 
   <ol>
 
-   <li><p class="big-issue">...</p></li>
+   <li><p class="XXX">...</p></li>
 
    <!-- During this step, the form data set is examined to ensure all
    the characters are representable in the submission character
@@ -29882,7 +29882,7 @@
 
   <ol>
 
-   <li><p class="big-issue">...</p></li>
+   <li><p class="XXX">...</p></li>
 
    <!-- During this step, the form data set is examined to ensure all
    the characters are representable in the submission character
@@ -29996,7 +29996,7 @@
   attribute must <span>reflect</span> the <code
   title="attr-details-open">open</code> content attribute.</p>
 
-  <p class="big-issue">Rendering will be described in the Rendering
+  <p class="XXX">Rendering will be described in the Rendering
   section in due course. Basically CSS :open and :closed match the
   element, it's a block-level element by default, and when it matches
   :closed it renders as if it had an XBL binding attached to it whose
@@ -30051,7 +30051,7 @@
    </dd>
   </dl>
 
-  <p class="big-issue">One possible thing to be added is a way to
+  <p class="XXX">One possible thing to be added is a way to
   detect when a row/selection has been deleted, activated, etc, by the
   user (delete key, enter key, etc).</p> <!-- XXXPA -->
 
@@ -30108,7 +30108,7 @@
   setting the <code title="attr-datagrid-disabled">disabled</code>
   attribute.</p>
 <!--XXXDND
-  <p class="big-issue">selection draggable [normative definitions are
+  <p class="XXX">selection draggable [normative definitions are
   in the interactive part below]</p>
 -->
 
@@ -30879,7 +30879,7 @@
     title="">row</var>, <var title="">cell</var>, <var
     title="">classes</var>)</code> method must add no classes.</p>
 
-    <p class="big-issue"><!-- select-provider-selection
+    <p class="XXX"><!-- select-provider-selection
     XXX-->autoselect some rows when initialized, reflect the selection
     in the select, reflect the multiple attribute somehow.</p>
 
@@ -31030,7 +31030,7 @@
     definitions below</a>, treating the row's element as being the
     cell's element.</p>
 
-    <p class="big-issue" id="generic-provider-selection">selection
+    <p class="XXX" id="generic-provider-selection">selection
     handling?</p>
 
     <p>The data provider must call the <code>datagrid</code>'s update
@@ -31223,7 +31223,7 @@
   fire a single <code title="event-load">load</code> event at itself,
   which doesn't bubble and cannot be canceled.</p>
 
-  <p class="big-issue">The end-tag parsing thing should be moved to
+  <p class="XXX">The end-tag parsing thing should be moved to
   the parsing section.</p>
 
   <p>The <code>datagrid</code> must then populate itself using the
@@ -31515,7 +31515,7 @@
    the <code>HTMLMenuElement</code> interface, i.e. a
    <code>menu</code> element DOM node. (This element must then be
    interpreted as described in the section on context menus to obtain
-   the actual context menu to use.<!-- XXXX update once menu section
+   the actual context menu to use.<!-- XXX update once menu section
    works; with xrefs -->) If the method returns something that is not
    an <code>HTMLMenuElement</code>, or if the method is not defined,
    then the row has no associated context menu. User agents may
@@ -31800,7 +31800,7 @@
   title="dom-datagrid-updateCellChanged">updateCellChanged()</code>
   method had been invoked, with the same row and column specified.</p>
 
-  <!-- XXXPA <p class="big-issue">define actions (performAction(), etc)</p> -->
+  <!-- XXXPA <p class="XXX">define actions (performAction(), etc)</p> -->
 
   <h5>The selection</h5>
 
@@ -31973,7 +31973,7 @@
 
   <p><em>This section only applies to interactive user agents.</em></p>
 
-  <p class="big-issue">define drag and drop in datagrids; selectiondraggable, etc.</p>
+  <p class="XXX">define drag and drop in datagrids; selectiondraggable, etc.</p>
 -->
 
 
@@ -32084,7 +32084,7 @@
 
   <div class="example">
 
-   <p class="big-issue">Need an example that shows an element that, if
+   <p class="XXX">Need an example that shows an element that, if
    double-clicked, invokes an action, but that also has a context
    menu, showing the various <code>command</code> attributes off, and
    that has a default command.</p>
@@ -32152,11 +32152,11 @@
   title="event-click">click</code> event at the element does not cause
   any of the actions described above to happen.</p>
 
-  <p class="big-issue"> should change all the above so it actually is
+  <p class="XXX"> should change all the above so it actually is
   just triggered by a click event, then we could remove the shadowing
   click() method and rely on actual events. </p>
 
-  <p class="big-issue">Need to define the command="" attribute</p>
+  <p class="XXX">Need to define the command="" attribute</p>
 
   <p class="note"><code>command</code> elements are not rendered
   unless they <span title="menu">form part of a menu</span>.</p>
@@ -32425,7 +32425,7 @@
 
   <p><em>This section is non-normative.</em></p>
 
-  <p class="big-issue">...</p>
+  <p class="XXX">...</p>
 
 <!--
 
@@ -32594,7 +32594,7 @@
 
   </dl>
 
-  <p class="big-issue">We should support <code>label</code> in the
+  <p class="XXX">We should support <code>label</code> in the
   algorithm above -- just iterate through the contents like with
   <code>li</code>, to support <code>input</code> elements in
   <code>label</code> elements. Also, <code>optgroup</code> elements
@@ -32646,7 +32646,7 @@
   does not, the default action must be for the user agent to show its
   default context menu, if it has one.</p>
 
-  <p class="big-issue">Context menus should inherit (so clicking on a
+  <p class="XXX">Context menus should inherit (so clicking on a
   span in a paragraph with a context menu should show the menu).</p>
 
   <p>If the element <em>does</em> have a context menu assigned, then
@@ -32781,7 +32781,7 @@
   can define a command also implements the <code
   title="command-ro">Command</code> interface:</p>
 
-  <p class="big-issue">Actually even better would be to just mix it
+  <p class="XXX">Actually even better would be to just mix it
   straight into those interfaces somehow.</p>
 
   <pre class="idl">[NoInterfaceObject] interface <dfn title="command-ro">Command</dfn> {<!--
@@ -33250,7 +33250,7 @@
 
   <p><em>This section is non-normative.</em></p>
 
-  <p class="big-issue">...examples...</p>
+  <p class="XXX">...examples...</p>
 
 
   <h4>The <dfn><code>datatemplate</code></dfn> element</h4>
@@ -34115,9 +34115,9 @@
 
   </ol>
 
-  <p class="big-issue">Define: <dfn>evaluated as a selector</dfn></p>
+  <p class="XXX">Define: <dfn>evaluated as a selector</dfn></p>
 
-  <p class="big-issue">Define: <dfn>text expansion algorithm for
+  <p class="XXX">Define: <dfn>text expansion algorithm for
   templates</dfn></p> <!-- this is basically used for expanding
   nodeValue values -->
 
@@ -34169,7 +34169,7 @@
   common to a group of consecutive elements.</p>
 
 
-  <p class="big-issue">Allowing <code>div</code> elements to contain
+  <p class="XXX">Allowing <code>div</code> elements to contain
   phrasing content makes it easy for authors to abuse
   <code>div</code>, using it with the <code>class=""</code> attribute
   to the point of not having any other elements in the markup. This is
@@ -35454,7 +35454,7 @@
   <p>A node is said to be <dfn>with script</dfn> if it is not
   <span>without script</span>.</p>
 
-  <p class="big-issue">If you can find a better pair of terms than
+  <p class="XXX">If you can find a better pair of terms than
   "with script" and "without script" let me know. The only things I
   can find that are less confusing are also way, way longer.</p>
 
@@ -35629,7 +35629,7 @@
 
   <h4>Security exceptions</h4>
 
-  <p class="big-issue">Define <dfn>security exception</dfn>.</p>
+  <p class="XXX">Define <dfn>security exception</dfn>.</p>
 
 
 
@@ -35721,7 +35721,7 @@
 
   <h4>Events</h4>
 
-  <p class="big-issue">We need to define how to handle events that are
+  <p class="XXX">We need to define how to handle events that are
   to be fired on a Document that is no longer the active document of
   its browsing context, and for Documents that have no browsing
   context. Do the events fire? Do the handlers in that document not
@@ -35796,7 +35796,7 @@
   reset the corresponding event handler attribute either.</p>
   <!-- http://software.hixie.ch/utilities/js/live-dom-viewer/?%3C!DOCTYPE%20html%3E%0A...%3Cbody%20onload%3D%22w(%27pass%27)%22%3E%0A%3Cscript%3Edocument.body.removeAttribute(%27onload%27)%3B%3C%2Fscript%3E -->
 
-  <p class="big-issue">How do we allow non-JS event handlers?</p>
+  <p class="XXX">How do we allow non-JS event handlers?</p>
 
   <p><dfn>Event handler DOM attributes</dfn>, on setting, must set the
   corresponding event handler attribute to their new value, and on
@@ -36088,7 +36088,7 @@
 
   <h5>Event firing</h5>
 
-  <p class="big-issue">maybe this should be moved higher up
+  <p class="XXX">maybe this should be moved higher up
   (terminology? conformance? DOM?) Also, the whole terminology thing
   should be changed so that we don't define any specific events here,
   we only define 'simple event', 'progress event', 'mouse event', 'key
@@ -36146,7 +36146,7 @@
   title="event-show">show</code> event</dfn> means <span title="fire a
   simple event">firing a simple event called <code
   title="event-show">show</code></span>. <span
-  class="big-issue">Actually this should fire an event that has
+  class="XXX">Actually this should fire an event that has
   modifier information (shift/ctrl etc), as well as having a pointer
   to the node on which the menu was fired, and with which the menu was
   associated (which could be an ancestor of the former).</span></p>
@@ -36167,7 +36167,7 @@
 
   <!-- XXX need to define the dispatching of DOMActivate -->
 
-  <p class="big-issue"><dfn title="fire a progress event">Firing a
+  <p class="XXX"><dfn title="fire a progress event">Firing a
   progress event called <var title="">e</var></dfn> means something
   that hasn't yet been defined, in the <a
   href="#refsPROGRESS">[PROGRESS]</a> spec.</p>
@@ -36175,7 +36175,7 @@
   <p>The default action of these event is to do nothing unless
   otherwise stated.</p>
 
-  <p class="big-issue">If you dispatch a custom "click" event at an
+  <p class="XXX">If you dispatch a custom "click" event at an
   element that would normally have default actions, should they get
   triggered? If so, we need to go through the entire spec and make
   sure that any default actions are defined in terms of <em>any</em>
@@ -37169,7 +37169,7 @@
 
   <p><em>This section is non-normative.</em></p>
 
-  <p class="big-issue">...</p>
+  <p class="XXX">...</p>
 
 
   <h4 id="appcache">Application caches</h4>
@@ -37781,7 +37781,7 @@
   specification) to start the <dfn>application cache update
   process</dfn>, the user agent must run the following steps:</p>
 
-  <p class="big-issue">the event stuff needs to be more consistent --
+  <p class="XXX">the event stuff needs to be more consistent --
   something about showing every step of the ui or no steps or
   something; and we need to deal with showing ui for browsing contexts
   that open when an update is already in progress, and we may need to
@@ -38584,7 +38584,7 @@
 
   </ol>
 
-  <p class="big-issue">We can make the add() API more usable
+  <p class="XXX">We can make the add() API more usable
   (i.e. make it possible to detect progress and distinguish success
   from errors without polling and timeouts) if we have the method
   return an object that is a target of Progress Events, much like the
@@ -39539,10 +39539,10 @@
 
   <ol>
 
-   <li><p class="big-issue">pause for scripts -- but don't use the
+   <li><p class="XXX">pause for scripts -- but don't use the
    "pause" definition since that involves not running script!</p></li>
 
-   <li><p class="big-issue">onbeforeunload, and if present set flag that we will kill document</p></li>
+   <li><p class="XXX">onbeforeunload, and if present set flag that we will kill document</p></li>
    <!--
    when we define onbeforeunload, then we have to say that the JS
    implementation of EventListener::handleEvent checks for that event,
@@ -39551,9 +39551,9 @@
    there isn't.
    -->
 
-   <li><p class="big-issue">onunload, and if present set flag that we will kill document</p></li>
+   <li><p class="XXX">onunload, and if present set flag that we will kill document</p></li>
 
-   <li><p class="big-issue">if flag is set: <span title="discard a document">discard the <code>Document</code></span></p></li>
+   <li><p class="XXX">if flag is set: <span title="discard a document">discard the <code>Document</code></span></p></li>
 
    <li>
 
@@ -39955,7 +39955,7 @@
 
     <ol>
 
-     <li class="big-issue">freeze any timers, intervals,
+     <li class="XXX">freeze any timers, intervals,
      XMLHttpRequests, database transactions, etc</li>
 
      <li>The user agent must move any properties that have been added
@@ -40019,7 +40019,7 @@
      <span>list of added properties</span> to browsing context's
      default view's <code>Window</code> object.</li>
 
-     <li class="big-issue">unfreeze any timers, intervals,
+     <li class="XXX">unfreeze any timers, intervals,
      XMLHttpRequests, database transactions, etc</li>
 
     </ol>
@@ -40060,26 +40060,26 @@
 
   </ol>
 
-  <p class="big-issue">how does the changing of the global attributes
+  <p class="XXX">how does the changing of the global attributes
   affect .watch() when seen from other Windows?</p>
 
 
   <h4>Closing a browsing context</h4>
 
-  <p class="big-issue">Closing a browsing context and discarding it
+  <p class="XXX">Closing a browsing context and discarding it
   (vs closing it and keeping it around in memory).</p>
 
-  <p class="big-issue">when a browsing context is closed, all session
+  <p class="XXX">when a browsing context is closed, all session
   history entries' <code>Document</code> objects must be
   discarded.</p>
 
-  <p class="big-issue">When a user agent is to <dfn>discard a
+  <p class="XXX">When a user agent is to <dfn>discard a
   <code>Document</code></dfn>, any frozen timers, intervals,
   XMLHttpRequests, database transactions, etc, must be killed, and any
   MessagePorts owned by the Window object must be
   unentangled.</p>
 
-  <p class="big-issue">Also, <code title="event-unload">unload</code>
+  <p class="XXX">Also, <code title="event-unload">unload</code>
   events should fire.</p>
 
 
@@ -40533,7 +40533,7 @@
 
   <p><em>This section is non-normative.</em></p>
 
-  <p class="big-issue">...</p>
+  <p class="XXX">...</p>
 
 <!-- include an example that does something like the following to show
 you should never embed strings straight into the statement, even when you
@@ -40748,7 +40748,7 @@
 
     <p>The result is <i>the statement</i>.</p>
 
-    <p class="big-issue">Implementation feedback is requested on what
+    <p class="XXX">Implementation feedback is requested on what
     to do with arguments that are of types that are not supported by
     the underlying SQL backend. For example, SQLite doesn't support
     booleans, so what should the UA do if passed a boolean? The Gears
@@ -40931,7 +40931,7 @@
 
   </table>
 
-  <p class="big-issue">We should define a more thorough list of
+  <p class="XXX">We should define a more thorough list of
   codes. Implementation feedback is requested to determine what codes
   are needed.</p>
 
@@ -42681,7 +42681,7 @@
 
   <p><em>This section is non-normative.</em></p>
 
-  <p class="big-issue">Would be nice to explain how these features
+  <p class="XXX">Would be nice to explain how these features
   work together.</p>
 
 
@@ -43306,7 +43306,7 @@
 
   <h4 id="textFieldSelection">APIs for the text field selections</h4>
 
-  <p class="big-issue">When we define HTMLTextAreaElement and
+  <p class="XXX">When we define HTMLTextAreaElement and
   HTMLInputElement we will have to add the IDL given below to both of
   their IDLs.</p>
 
@@ -43787,7 +43787,7 @@
 
   <p><em>This section is non-normative.</em></p>
 
-  <p class="big-issue">It's also currently non-existent.</p>
+  <p class="XXX">It's also currently non-existent.</p>
 
 
   <h4>The <code>DragEvent</code> and <code>DataTransfer</code> interfaces</h4>
@@ -43801,7 +43801,7 @@
   void <span title="dom-DragEvent-initDragEventNS">initDragEventNS</span>(in DOMString namespaceURIArg, in DOMString typeArg, in boolean canBubbleArg, in boolean cancelableArg, in AbstractView viewArg, in long detailArg, in <span>DataTransfer</span> dataTransferArg);
 };</pre>
 
-  <p class="big-issue">We should have modifier key information in here too
+  <p class="XXX">We should have modifier key information in here too
   (shift/ctrl, etc), like with mouse events and like with the context
   menu event.</p>
 
@@ -44155,7 +44155,7 @@
   be fired on the deepest node that is a common ancestor of all parts
   of the selection.</p>
 
-  <p class="big-issue">We should look into how browsers do other types
+  <p class="XXX">We should look into how browsers do other types
   (e.g. Firefox apparently also adds text/html for internal drag and
   drop of a selection).</p>
 
@@ -44768,7 +44768,7 @@
 
   <h3 id="undo"><dfn>Undo history</dfn></h3>
 
-  <p class="big-issue">There has got to be a better way of doing this, surely.</p>
+  <p class="XXX">There has got to be a better way of doing this, surely.</p>
 
   <p>The user agent must associate an <dfn>undo transaction
   history</dfn> with each <code>HTMLDocument</code> object.</p>
@@ -44813,7 +44813,7 @@
 
   <h4>The <code>UndoManager</code> interface</h4>
 
-  <div class="big-issue">
+  <div class="XXX">
 
    <p>This API sucks. Seriously. It's a terrible API. Really bad. I
    hate it. Here are the requirements:</p>
@@ -44922,7 +44922,7 @@
   title="dom-UndoManager-clearRedo">clearRedo()</code> had been
   called).</p>
 
-  <p class="big-issue">We could fire events when someone adds
+  <p class="XXX">We could fire events when someone adds
   something to the undo history -- one event per undo object entry
   before the position (or after, during redo addition), allowing the
   script to decide if that entry should remain or not. Or
@@ -44953,7 +44953,7 @@
   <span>DOM changes</span> entries or <span>undo object</span>
   entries.</p>
 
-  <p class="big-issue">Another idea is to have a way for scripts to
+  <p class="XXX">Another idea is to have a way for scripts to
   say "startBatchingDOMChangesForUndo()" and after that the changes to
   the DOM go in as if the user had done them.</p>
 
@@ -46121,7 +46121,7 @@
 
   <p><em>This section is non-normative.</em></p>
 
-  <p class="big-issue">An introduction to the client-side and
+  <p class="XXX">An introduction to the client-side and
   server-side of using the direct connection APIs.</p>
 
 
@@ -46471,7 +46471,7 @@
     string "Upgrade: WebSocket", CRLF, the string
     "Connection: Upgrade", CRLF.</p>
 
-    <p class="big-issue">What if the response is a 401 asking for
+    <p class="XXX">What if the response is a 401 asking for
     credentials?</p>
 
    </li>
@@ -46856,7 +46856,7 @@
 
   </ol>
 
-  <p class="big-issue">People often request the ability to send binary
+  <p class="XXX">People often request the ability to send binary
   blobs over this API; also, once the other postMessage() methods
   support it, we should look into allowing name/value pairs, arrays,
   and numbers using postMessage() instead of just strings and binary
@@ -47357,7 +47357,7 @@
 
   <h4>Posting structured data</h4>
 
-  <p class="big-issue">People often request the ability to send
+  <p class="XXX">People often request the ability to send
   name/value pairs, arrays, and numbers using postMessage() instead of
   just strings.</p>
 
@@ -47370,7 +47370,7 @@
 
   <p><em>This section is non-normative.</em></p>
 
-  <p class="big-issue">An introduction to the channel and port
+  <p class="XXX">An introduction to the channel and port
   APIs.</p>
 
 
@@ -47591,7 +47591,7 @@
 
   </ol>
 
-  <p class="big-issue">People often request the ability to send
+  <p class="XXX">People often request the ability to send
   name/value pairs, arrays, and numbers using postMessage() instead of
   just strings.</p>
 
@@ -51941,7 +51941,7 @@
     title="insertion mode: before head">before head</span>", then
     reprocess the current token.</p>
 
-    <p class="big-issue">Should probably make end tags be ignored, so
+    <p class="XXX">Should probably make end tags be ignored, so
     that "</head><!-- --><html>" puts the comment before the
     root node (or should we?)</p>
 
@@ -52204,7 +52204,7 @@
     <p>Act as if an end tag token with the tag name "head" had
     been seen, and reprocess the current token.</p>
 
-    <p class="big-issue">In certain UAs, <a
+    <p class="XXX">In certain UAs, <a
     href="https://bugzilla.mozilla.org/attachment.cgi?id=180157&action=view">some
     elements</a> don't trigger the "in body" mode straight away,
     but instead get put into the head. Do we want to copy
@@ -53102,7 +53102,7 @@
 
 <!--XXX
     <div class="example">
-     <p class="big-issue">Need an example.</p>
+     <p class="XXX">Need an example.</p>
     </div>
 -->
 
@@ -53374,7 +53374,7 @@
     keywords here: (input field)" in the user's preferred
     language.</p>
 
-    <p class="big-issue"> Then need to specify that if the form
+    <p class="XXX"> Then need to specify that if the form
     submission causes just a single form control, whose name is
     "isindex", to be submitted, then we submit just the value part,
     not the "isindex=" part.  </p>
@@ -55018,7 +55018,7 @@
 
   </dl>
 
-  <p class="big-issue">This doesn't handle UAs that don't support
+  <p class="XXX">This doesn't handle UAs that don't support
   frames, or that do support frames but want to show the NOFRAMES
   content. Supporting the former is easy; supporting the latter is
   harder.</p>
@@ -55151,7 +55151,7 @@
 
   <!-- XXX make sure things "delay the load event" -->
 
-  <p class="big-issue">delaying the load event for things like image
+  <p class="XXX">delaying the load event for things like image
   loads allows for intranet port scans (even without
   javascript!). Should we really encode that into the spec?</p>
 
@@ -55832,7 +55832,7 @@
 
   -->
 
-  <p class="big-issue">This section will probably include details on
+  <p class="XXX">This section will probably include details on
   how to render DATAGRID (including <span id="datagridPseudos">its
   pseudo-elements</span>), drag-and-drop, etc, in a visual medium, in
   concert with CSS. Terms that need to be defined include: <dfn>sizing
@@ -55885,12 +55885,12 @@
 -->
 
 
-  <p class="big-issue"> must define letting the user "<dfn>obtain a
+  <p class="XXX"> must define letting the user "<dfn>obtain a
   physical form</dfn> (or a representation of a physical form)" of a
   document (printing) and what this means for the UA, in particular
   creating a new view for the print media.</p>
 
-  <p class="big-issue">Must define that in CSS, tag and attribute
+  <p class="XXX">Must define that in CSS, tag and attribute
   names in HTML documents, and class names in quirks mode documents,
   are case-insensitive, as well as saying which attribute values must
   be compared case-insensitively.</p>
@@ -55898,7 +55898,7 @@
 
   <h3>Rendering and the DOM</h3>
 
-  <p class="big-issue">This section is wrong. mediaMode will end up on
+  <p class="XXX">This section is wrong. mediaMode will end up on
   Window, I think. All views implement Window.</p>
 
   <p>Any object implement the <code>AbstractView</code> interface must
@@ -55942,7 +55942,7 @@
 
   <h4>The <code>body</code> element</h4>
 
-  <p class="big-issue">Need to define the content attributes in terms
+  <p class="XXX">Need to define the content attributes in terms
   of CSS or something.</p>
 
   <pre class="idl">[XXX] interface <span>HTMLDocument</span> {
@@ -56032,7 +56032,7 @@
   document</span>, then the element must be ignored (it represents
   nothing).</p>
 
-  <p>Otherwise, <span class="big-issue">define how the element works,
+  <p>Otherwise, <span class="XXX">define how the element works,
   if supported</span>.</p>
 
   <pre class="idl">[XXX] interface <span>HTMLDocument</span> {
@@ -56087,7 +56087,7 @@
 
   <h3 id="timers">Timers</h3>
 
-  <p class="big-issue">This section is expected to be moved to its own
+  <p class="XXX">This section is expected to be moved to its own
   specification in due course. It needs a lot of work to actually make
   it into a semi-decent spec.</p>
 
@@ -56134,7 +56134,7 @@
   title="">code</var>, <var title="">timeout</var>[, <var
   title="">language</var>])</code></dfn> may be used. This variant
   takes a string instead of a <code>TimeoutHandler</code>
-  object. <span class="big-issue">define the actual requirements for
+  object. <span class="XXX">define the actual requirements for
   this method, as with the previous one.</span> That string must be
   parsed using the specified <var title="">language</var> (defaulting
   to ECMAScript if the third argument is omitted) and executed in the
@@ -56142,7 +56142,7 @@
   <code>Window</code> object on which the <code
   title="setTimeout">setTimeout()</code> method was invoked.</p>
 
-  <p class="big-issue">Need to define <var title="">language</var>
+  <p class="XXX">Need to define <var title="">language</var>
   values.</p>
 
   <p>The <dfn
@@ -56174,19 +56174,18 @@
 
   <p><em>This section is non-normative.</em></p>
 
-  <p class="big-issue">List of elements</p>
+  <p class="XXX">List of elements</p>
 
-  <p class="big-issue">List of attributes</p>
+  <p class="XXX">List of attributes</p>
 
-  <p class="big-issue">List of interfaces</p>
+  <p class="XXX">List of interfaces</p>
 
-  <p class="big-issue">List of events</p>
+  <p class="XXX">List of events</p>
 
 
   <h2 class="no-num" id="references">References</h2>
 
-  <p class="big-issue">This section will be written in a future
-  draft.<!--XXX--></p>
+  <p class="XXX">This section will be written in a future draft.</p>
 
   <!-- XXX check that #refsRFC([0-9]+) is always for [RFC\1] -->
 




More information about the Commit-Watchers mailing list