HTML Standard Tracker

Filter

File a bug

SVNBugCommentTime (UTC)
2239WF2: <input type=datetime min> and <input type=datetime max>.2008-09-25 10:47
@@ -26530,31 +26530,70 @@ function AddCloud(data, x, y) { ... }</pre>
   UTC date and time</span> representing the user's selection. User
   agents should allow the user to set the <span
   title="concept-fe-value">value</span> to the empty string.</p>
 
   <p><strong>The <span title="attr-input-type-datetime">Date and
   Time</span> state's <span>value sanitization algorithm</span> is as
   follows:</strong> If the <span title="concept-fe-value">value</span>
   of the element is not a <span>valid UTC date and time</span>, then
   set it to the empty string instead.</p>
 
+  <p>The <dfn title="concept-input-value-datetime">selected UTC date
+  and time</dfn> is the result of <span title="parse a UTC date and
+  time">parsing a UTC date and time</span> from the element's <span
+  title="concept-fe-value">value</span>, unless that fails, in which
+  case there is no <span title="concept-input-value-datetime">selected
+  UTC date and time</span>.</p>
+
   <p class="big-issue"><strong>The <span
   title="attr-input-type-datetime">Date and Time</span> state's
   <span><code title="dom-input-valueAsDate">valueAsDate</code> setter
   algorithm</span> is as follows:</strong> ...</p>
 
   <p class="big-issue"><strong>The <span
   title="attr-input-type-datetime">Date and Time</span> state's
   <span><code title="dom-input-valueAsNumber">valueAsNumber</code>
   setter algorithm</span> is as follows:</strong> ...</p>
 
-  <p class="big-issue"> min, max, step; how to parse them, what they do </p>
+  <p>The <code title="attr-input-min">min</code> attribute, if
+  specified, must have a value that is a <span>valid UTC date and
+  time</span>. The <dfn title="concept-input-min-datetime">minimum UTC
+  date and time</dfn> is the result of <span title="parse a UTC date
+  and time">parsing a UTC date and time</span> from the element's
+  <code title="attr-input-min">min</code> attribute, unless that
+  fails, in which case there is no <span
+  title="concept-input-min-datetime">minimum UTC date and
+  time</span>.</p>
+
+  <p><strong>Constraint validation:</strong> When there is both a
+  <span title="concept-input-value-datetime">selected UTC date and
+  time</span> and a <span title="concept-input-min-datetime">minimum
+  UTC date and time</span>, if the former is less than the latter, the
+  element is <span>suffering from an underflow</span>.</p>
+
+  <p>The <code title="attr-input-max">max</code> attribute, if
+  specified, must have a value that is a <span>valid UTC date and
+  time</span>. The <dfn title="concept-input-max-datetime">maximum UTC
+  date and time</dfn> is the result of <span title="parse a UTC date
+  and time">parsing a UTC date and time</span> from the element's
+  <code title="attr-input-max">max</code> attribute, unless that
+  fails, in which case there is no <span
+  title="concept-input-max-datetime">maximum UTC date and
+  time</span>.</p>
+
+  <p><strong>Constraint validation:</strong> When there is both a
+  <span title="concept-input-value-datetime">selected UTC date and
+  time</span> and a <span title="concept-input-max-datetime">maximum
+  UTC date and time</span>, if the former is more than the latter, the
+  element is <span>suffering from an overflow</span>.</p>
+
+  <p class="big-issue">... <code title="attr-input-step">step</code></p>
 
   <p>When an <code>input</code> element's <code
   title="attr-input-type">type</code> attribute is in the <span
   title="attr-input-type-datetime">Date and Time</span> state, the
   following common <code>input</code> element content attributes, DOM
   attributes, and methods apply to the element:
   <code title="attr-input-autocomplete">autocomplete</code>,
   <code title="attr-input-list">list</code>,
   <code title="attr-input-max">max</code>,
   <code title="attr-input-min">min</code>,
@@ -26940,20 +26979,35 @@ rel="" on submit buttons?
   attribute is a <span>boolean attribute</span>. When specified, the
   element is <i title="concept-input-immutable">immutable</i>.</p>
 
   <p><strong>Constraint validation:</strong> If the <code
   title="attr-input-readonly">readonly</code> attribute is specified
   on an <code>input</code> element, the element is <span>barred from
   constraint validation</span>.</p>
 
 
 
+  <h6>Other attributes</h6>
+
+  <p>The <dfn title="attr-input-min"><code>min</code></dfn> and <dfn
+  title="attr-input-max"><code>max</code></dfn> attributes define a
+  range constraint on the value.</p>
+
+  <p>The <dfn title="attr-input-step"><code>step</code></dfn>
+  attribute defines the increments between allowed values.</p>
+
+  <p>These attributes apply for a number of different states, but as
+  their behavior varies from state to state, they are not defined here
+  but instead in the states' own sections.</p>
+
+
+
   <h5>Common <code>input</code> element APIs</h5>
 
   <h6>Value manipulation</h6>
 
   <p>The <dfn title="dom-input-value"><code>value</code></dfn> DOM
   attribute allows scripts to manipulate the <span
   title="concept-fe-value">value</span> of an <code>input</code>
   element. On getting, it must return the current <span
   title="concept-fe-value">value</span> of the element. On setting,
   it must set the element's <span
@@ -27647,20 +27701,27 @@ interface <dfn>HTMLOptionElement</dfn> : <span>HTMLElement</span> {
 
   <p class="big-issue">An element <dfn
   title="concept-fv-valid">satisfies its constraints</dfn> if ...</p>
 
   <p class="big-issue">... <dfn>suffering from a type
   mismatch</dfn></p>
 
   <p class="big-issue">... <dfn>suffering from being too
   long</dfn></p>
 
+  <p class="big-issue">... <dfn>suffering from on underflow</dfn></p>
+
+  <p class="big-issue">... <dfn>suffering from on overflow</dfn></p>
+
+  <p class="big-issue">... <dfn>suffering from a step
+  mismatch</dfn></p>
+
 
 
   <h5>Constraint validation</h5>
 
   <p>When the user agent is required to <dfn>statically validate the
   constraints</dfn> of <code>form</code> element <var
   title="">form</var>, it must run the following steps, which return
   either a <i>positive</i> result (all the controls in the form are
   valid) or a <i>negative</i> result (there are invalid controls)
   along with a (possibly empty) list of elements that are invalid and

|