Removed browser references in normative text.

Also classified a note as class="note".

Author: Rune Lillesveen

css-device-adapt/Overview.html

@@ -17,7 +17,7 @@
 
    <h1>CSS Device Adaptation</h1>
 
-   <h2 class="no-num no-toc" id=longstatus-date>Editor's Draft 10 May 2011</h2>
+   <h2 class="no-num no-toc" id=longstatus-date>Editor's Draft 2 June 2011</h2>
 
    <dl>
     <dt>This version:
@@ -1255,29 +1255,17 @@ <h3 id=definitions><span class=secno>6.1. </span>Definitions</h3>
   <p> <code class=index id=initial-width
    title="width!!initial">initial-width</code> is the width of the <a
    href="#initial-viewport">initial viewport</a> in pixels at zoom factor
-   1.0. <span class=note>On a device this is typically (<code>device-width -
-   decorations</code>). On Safari/iPhone this is identical to the
-   device-width.</span>
+   1.0.
 
   <p> <code class=index id=initial-height
    title="height!!initial">initial-height</code> is the height of the <a
    href="#initial-viewport">initial viewport</a> in pixels at zoom factor
-   1.0. <span class=note>Typically (<code>device-height -
-   decorations</code>).</span>
+   1.0.
 
   <h3 id=constraining-procedure><span class=secno>6.2. </span>The procedure</h3>
 
   <p>The used values are resolved from the computed values going through the
-   steps below. <span class=note>The procedure is closely modelled after the
-   behavior of the Safari/iPhone browser. We have run tests on the Android
-   SDK browser and a Fennec nightly build for Windows to see where the
-   various implementations are the same and where they differ. We found that
-   the Safari implementation is by far the most consistent and predictable,
-   and decided to ignore the other implementations for this specification.
-   This procedure, and the <a href="#parsing-algorithm">parsing
-   algorithm</a>, are backed up by a compliance test suite currently
-   consisting of 120-130 tests. All but one pass in the <a
-   href="#tested-safari">tested Safari browser</a>.</span>
+   steps below.
 
   <p>User agents are expected, but not required, to re-run this procedure and
    re-layout the document, if necessary, in response to changes in the user
@@ -1901,8 +1889,9 @@ <h4 class="no-num no-toc" id=the-target-densitydpi-property>The <code
   <p class=issue>At risk since &lsquo;<a href="#resolution"><code
    class=property>resolution</code></a>&rsquo; is at risk.
 
-  <p>This property differ from the others since it is from the WebKit
-   implementation used in the Android browser and not supported in the Safari
+  <p class=note>This property differ from the others since it is from the
+   WebKit implementation used in the Android browser and not supported in
+   Safari
 
   <p>The <code class=index id=target-densitydpi1>target-densityDpi</code>
    property is translated into &lsquo;<a href="#resolution"><code
@@ -2041,7 +2030,7 @@ <h2 class=no-num id=property-index>Property index</h2>
      <th>Media
 
    <tbody>
-    <tr valign=baseline>
+    <tr>
      <td><a class=property href="#height">height</a>
 
      <td>&lt;viewport-length&gt;{1,2}
@@ -2056,7 +2045,7 @@ <h2 class=no-num id=property-index>Property index</h2>
 
      <td>visual, continuous
 
-    <tr valign=baseline>
+    <tr>
      <td><a class=property href="#max-height">max-height</a>
 
      <td>&lt;viewport-length&gt;
@@ -2071,7 +2060,7 @@ <h2 class=no-num id=property-index>Property index</h2>
 
      <td>visual, continuous
 
-    <tr valign=baseline>
+    <tr>
      <td><a class=property href="#max-width">max-width</a>
 
      <td>&lt;viewport-length&gt;
@@ -2086,7 +2075,7 @@ <h2 class=no-num id=property-index>Property index</h2>
 
      <td>visual, continuous
 
-    <tr valign=baseline>
+    <tr>
      <td><a class=property href="#max-zoom">max-zoom</a>
 
      <td>auto | &lt;number&gt; | &lt;percentage&gt;
@@ -2101,7 +2090,7 @@ <h2 class=no-num id=property-index>Property index</h2>
 
      <td>visual, continuous
 
-    <tr valign=baseline>
+    <tr>
      <td><a class=property href="#min-height">min-height</a>
 
      <td>&lt;viewport-length&gt;
@@ -2116,7 +2105,7 @@ <h2 class=no-num id=property-index>Property index</h2>
 
      <td>visual, continuous
 
-    <tr valign=baseline>
+    <tr>
      <td><a class=property href="#min-width">min-width</a>
 
      <td>&lt;viewport-length&gt;
@@ -2131,7 +2120,7 @@ <h2 class=no-num id=property-index>Property index</h2>
 
      <td>visual, continuous
 
-    <tr valign=baseline>
+    <tr>
      <td><a class=property href="#min-zoom">min-zoom</a>
 
      <td>auto | &lt;number&gt; | &lt;percentage&gt;
@@ -2146,7 +2135,7 @@ <h2 class=no-num id=property-index>Property index</h2>
 
      <td>visual, continuous
 
-    <tr valign=baseline>
+    <tr>
      <td><a class=property href="#orientation">orientation</a>
 
      <td>auto | portrait | landscape
@@ -2161,7 +2150,7 @@ <h2 class=no-num id=property-index>Property index</h2>
 
      <td>visual, continuous
 
-    <tr valign=baseline>
+    <tr>
      <td><a class=property href="#resolution">resolution</a>
 
      <td>auto | device | &lt;resolution&gt;
@@ -2176,7 +2165,7 @@ <h2 class=no-num id=property-index>Property index</h2>
 
      <td>visual, continuous
 
-    <tr valign=baseline>
+    <tr>
      <td><a class=property href="#user-zoom">user-zoom</a>
 
      <td>zoom | fixed
@@ -2191,7 +2180,7 @@ <h2 class=no-num id=property-index>Property index</h2>
 
      <td>visual, continuous
 
-    <tr valign=baseline>
+    <tr>
      <td><a class=property href="#width">width</a>
 
      <td>&lt;viewport-length&gt;{1,2}
@@ -2206,7 +2195,7 @@ <h2 class=no-num id=property-index>Property index</h2>
 
      <td>visual, continuous
 
-    <tr valign=baseline>
+    <tr>
      <td><span class=property>zoom</span>
 
      <td>auto | &lt;number&gt; | &lt;percentage&gt;

css-device-adapt/Overview.src.html

@@ -1048,30 +1048,17 @@ <h3>Definitions</h3>
     <p>
       <code class="index" title="width!!initial">initial-width</code> is the
       width of the <span>initial viewport</span> in pixels at zoom factor 1.0.
-      <span class="note">On a device this is typically (<code>device-width
-      - decorations</code>). On Safari/iPhone this is identical to the
-      device-width.</span>
     </p>
 
     <p>
       <code class="index" title="height!!initial">initial-height</code> is the
       height of the <span>initial viewport</span> in pixels at zoom factor 1.0.
-      <span class="note">Typically (<code>device-height - decorations</code>).</span>
     </p>
 
     <h3 id="constraining-procedure">The procedure</h3>
 
     <p>The used values are resolved from the computed values going
-      through the steps below. <span class="note">The procedure is closely
-      modelled after the behavior of the Safari/iPhone browser. We have run
-      tests on the Android SDK browser and a Fennec nightly build for Windows to
-      see where the various implementations are the same and where they differ.
-      We found that the Safari implementation is by far the most
-      consistent and predictable, and decided to ignore the other
-      implementations for this specification. This procedure, and the
-      <a href="#parsing-algorithm">parsing algorithm</a>, are backed up by a
-      compliance test suite currently consisting of 120-130 tests. All but one
-      pass in the <a href="#tested-safari">tested Safari browser</a>.</span></p>
+      through the steps below.</p>
 
     <p>User agents are expected, but not required, to re-run this procedure and
       re-layout the document, if necessary, in response to changes in the user
@@ -1621,8 +1608,8 @@ <h4 class="no-num no-toc">The <code class="index">target-densityDpi</code> prope
 
     <p class="issue">At risk since &lsquo;<code class="property">resolution</code>&rsquo; is at risk.</p>
 
-    <p>This property differ from the others since it is from the WebKit
-      implementation used in the Android browser and not supported in the Safari</p>
+    <p class="note">This property differ from the others since it is from the WebKit
+      implementation used in the Android browser and not supported in Safari</p>
 
     <p>The <code class="index">target-densityDpi</code> property is translated
       into &lsquo;<code class="property">resolution</code>&rsquo; with the