ACTION-31: Remove restriction on rotationAngle and add explanation.
Also, replace the mathematical range notation with English, because the
notation was not defined.
These changes were discussed in the 2011-04-12 telcon and at
http://lists.w3.org/Archives/Public/public-webevents/2011AprJun/0020.html
--- a/test/touchevents/touch-area.html Tue Apr 12 09:46:04 2011 -0700
+++ b/test/touchevents/touch-area.html Tue Apr 12 09:56:23 2011 -0700
@@ -17,12 +17,6 @@
assert_true(t.rotationAngle >= 0 && t.rotationAngle < 90);
}, "rotationAngle must be in the range [0, 90).");
- test(function() {
- assert_true(t.radiusX != t.radiusY || t.rotationAngle == 0);
- },
- "If the ellipse described by radiusX and radiusY is circular, " +
- "then rotationAngle must be 0.");
-
done();
});
}
--- a/touchevents.html Tue Apr 12 09:46:04 2011 -0700
+++ b/touchevents.html Tue Apr 12 09:56:23 2011 -0700
@@ -176,12 +176,16 @@
<p>
the angle (in degrees) that the ellipse described by <a>radiusX</a>
and <a>radiusY</a> is rotated clockwise about its center;
- <code>0</code> if no value is known. The value must be in the
- range <code>[0, 90)</code>.
+ <code>0</code> if no value is known. The value must be greater
+ than or equal to <code>0</code> and less than <code>90</code>.
</p>
<p>
If the ellipse described by <a>radiusX</a> and <a>radiusY</a> is
- circular, then <a>rotationAngle</a> must be <code>0</code>.
+ circular, then <a>rotationAngle</a> has no effect. The user agent
+ may use <code>0</code> as the value in this case, or it may use any
+ other value in the allowed range. (For example, the user agent may
+ use the value from the previous touch event, to avoid sudden
+ changes in value.)
</p>
</dd>