[Bug 22467] New: <select> should have “oninput”

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

            Bug ID: 22467
           Summary: <select> should have “oninput”
    Classification: Unclassified
           Product: HTML WG
           Version: unspecified
          Hardware: PC
                OS: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: HTML5 spec
          Assignee: dave.null@w3.org
          Reporter: felipe@felipegasper.com
        QA Contact: public-html-bugzilla@w3.org
                CC: mike@w3.org, public-html-admin@w3.org,
                    public-html-wg-issue-tracking@w3.org

It’s hugely unintuitive that <select> inputs don’t fire an “oninput” event.

Anything that can affect the form’s submitted data should be firing “oninput”
to simplify form validation etc.



Test case:


<!DOCTYPE html>
<html>
<head>
<meta charset="utf-8">
</head>
<body>
    <form action="javascript:void(0)" oninput="console.log(this)">
        <label>Changing this doesn’t fire “oninput”:
            <select name="foo"><option>1</option><option>2</option></select>
        </label>
        <br>
        <br>
        <label>… but changing this does:
            <input type="text" name="bar">
        </label>
    </form>
</body>
</html>

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

Received on Tuesday, 25 June 2013 21:31:46 UTC