W3C home > Mailing lists > Public > public-html-admin@w3.org > November 2014

[Bug 27432] New: The current [WHATWG] spec text for <input type=number> stepping can cause stepping in the opposite direction to the one requested

From: <bugzilla@jessica.w3.org>
Date: Tue, 25 Nov 2014 17:08:12 +0000
To: public-html-admin@w3.org
Message-ID: <bug-27432-2495@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=27432

            Bug ID: 27432
           Summary: The current [WHATWG] spec text for <input type=number>
                    stepping can cause stepping in the opposite direction
                    to the one requested
           Product: HTML WG
           Version: unspecified
          Hardware: PC
                OS: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: HTML5 spec
          Assignee: dave.null@w3.org
          Reporter: jwatt@jwatt.org
        QA Contact: public-html-bugzilla@w3.org
                CC: mike@w3.org, public-html-admin@w3.org,
                    public-html-wg-issue-tracking@w3.org

Right now Mozilla's <input type=number> stepping code has checks and tests to
make sure that a step up never causes the value to decrease, and a step down
never causes the value to increase. The current spec text seems to cause this
to happen in certain circumstances. For example,

  data:text/html,<input type=number value=1 max=0>

Actually, checking Chrome I see that they prevent a stepUp() on that example
from changing the value too, so it's not just Firefox.

We essentially prevent this by having a step between steps 8 and 9 that causes
us to abort if we're doing a step up and 'value' is less than the value before
the step was initiated, and a similar check for step down.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Received on Tuesday, 25 November 2014 17:08:16 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:57:30 UTC