[Bug 21265] New: Be more strict/clear for 'explicit commit action' for the change event

https://www.w3.org/Bugs/Public/show_bug.cgi?id=21265

            Bug ID: 21265
           Summary: Be more strict/clear for 'explicit commit action' for
                    the change event
    Classification: Unclassified
           Product: HTML WG
           Version: unspecified
          Hardware: PC
                OS: Windows NT
            Status: NEW
          Severity: normal
          Priority: P2
         Component: HTML5 spec
          Assignee: dave.null@w3.org
          Reporter: alexander.farkas@aperto.de
        QA Contact: public-html-bugzilla@w3.org
                CC: mike@w3.org, public-html-admin@w3.org,
                    public-html-wg-issue-tracking@w3.org

The bug explains the explicit commit action with two examples. (see:
http://www.w3.org/TR/html5/forms.html#event-input-change) In the second example
it says:

"... a Date control that allows both text-based user input and user selection
from a drop-down calendar: while text input might not have an explicit commit
step, ..."

I think the "might" should be changed to either "should" or "must". i.e.:

"... a Date control that allows both text-based user input and user selection
from a drop-down calendar: while text input *must* not have an explicit commit
step, ..."

It would be also great to explain an explicit commit action in case of an
input[type="range"]. Because both current examples involve a "popover menu"
(file select, date calendar). While a range has a totally different UI. For
example, while the user holds the mouse and is dragging, he hasn't commited a
change (only input event occurs). As soon as the user releases his mouse button
(mousup, touchend, keyup etc.), he has commited a change.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Wednesday, 13 March 2013 13:08:17 UTC