[html5] r7787 - [e] (0) Clarify this to make it clear that Chrome and IE's behaviours are wrong [...]

[whatwg at whatwg.org]

Author: ianh
Date: 2013-04-01 11:20:08 -0700 (Mon, 01 Apr 2013)
New Revision: 7787

Modified:
   complete.html
   index
   source
Log:
[e] (0) Clarify this to make it clear that Chrome and IE's behaviours are wrong with <input type=range onchange>.
Fixing https://www.w3.org/Bugs/Public/show_bug.cgi?id=21377
Affected topics: HTML

Modified: complete.html
===================================================================
--- complete.html	2013-04-01 18:02:42 UTC (rev 7786)
+++ complete.html	2013-04-01 18:20:08 UTC (rev 7787)
@@ -50007,6 +50007,11 @@
   selecting a date from the drop down calendar and then dismissing the drop down would be a commit
   action.</p>
 
+  <p class=example>A third example of a user interface with a commit action would be a <a href="#range-state-(type=range)" title=attr-input-type-range>Range</a> controls that use a slider. While the user is dragging
+  the control's knob, <code title=event-input>input</code> events would fire whenever the position
+  changed, whereas the <code title=event-change>change</code> event would only fire when the user
+  let go of the knob, committing to a specific value.</p>
+
   <p>When the user agent changes the element's <a href=#concept-fe-value title=concept-fe-value>value</a> on behalf
   of the user (e.g. as part of a form prefilling feature), the user agent must follow these
   steps:</p>

Modified: index
===================================================================
--- index	2013-04-01 18:02:42 UTC (rev 7786)
+++ index	2013-04-01 18:20:08 UTC (rev 7787)
@@ -50007,6 +50007,11 @@
   selecting a date from the drop down calendar and then dismissing the drop down would be a commit
   action.</p>
 
+  <p class=example>A third example of a user interface with a commit action would be a <a href="#range-state-(type=range)" title=attr-input-type-range>Range</a> controls that use a slider. While the user is dragging
+  the control's knob, <code title=event-input>input</code> events would fire whenever the position
+  changed, whereas the <code title=event-change>change</code> event would only fire when the user
+  let go of the knob, committing to a specific value.</p>
+
   <p>When the user agent changes the element's <a href=#concept-fe-value title=concept-fe-value>value</a> on behalf
   of the user (e.g. as part of a form prefilling feature), the user agent must follow these
   steps:</p>

Modified: source
===================================================================
--- source	2013-04-01 18:02:42 UTC (rev 7786)
+++ source	2013-04-01 18:20:08 UTC (rev 7787)
@@ -59354,6 +59354,12 @@
   selecting a date from the drop down calendar and then dismissing the drop down would be a commit
   action.</p>
 
+  <p class="example">A third example of a user interface with a commit action would be a <span
+  title="attr-input-type-range">Range</span> controls that use a slider. While the user is dragging
+  the control's knob, <code title="event-input">input</code> events would fire whenever the position
+  changed, whereas the <code title="event-change">change</code> event would only fire when the user
+  let go of the knob, committing to a specific value.</p>
+
   <p>When the user agent changes the element's <span title="concept-fe-value">value</span> on behalf
   of the user (e.g. as part of a form prefilling feature), the user agent must follow these
   steps:</p>