New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 534245 link

Starred by 11 users

Issue metadata

Status: Fixed
Last visit > 30 days ago
Closed: Jan 2018
EstimatedDays: ----
NextAction: ----
OS: All
Pri: 2
Type: Bug

Sign in to add a comment

<input> of type=checkbox,radio,file doesn't fire `input` events

Reported by, Sep 21 2015

Issue description

Chrome Version       : 45.0.2454.93
OS Version: OS X 10.10.5
URLs (if applicable) :,output
UserAgentString: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/45.0.2454.93 Safari/537.36

Per the following portions of the HTML specification:

when the user changes the checkedness of an <input type="checkbox"> or <input type="radio">, or when a user changes the selected files of an <input type="file">, the browser is supposed to fire an `input` event ( ) at that <input> element.
Chrome doesn't currently comply with this, and doesn't fire `input` events in these cases.

What steps will reproduce the problem?
1. Open,output in Chrome.
2. Check the checkbox.
3. Click one of the two radio buttons.
4. Click "Choose File" and select a file.

What is the expected result?
After each of steps 2 thru 4, an alert box with the message "input!" should be displayed (because an `input` event should be fired at the respective <input> element).

What happens instead of that?
No alert boxes are shown because no `input` events were fired.

Labels: Cr-Blink-Forms Needs-Feedback
Thanks for the report. I am observing the similar behavior across browsers Firefox 39, Safari 8 & IE11, no alert is displayed after steps 2. Request you to please confirm the same.

I really appreciate your help

Thank you!

Comment 2 by, Sep 21 2015

Labels: -Pri-2 Pri-4
Status: Available

Comment 3 by, Sep 21 2015

> Thanks for the report. I am observing the similar behavior across browsers
> Firefox 39, Safari 8 & IE11, no alert is displayed after steps 2. Request you
> to please confirm the same.

Yes, the other browsers don't seem to correctly implement this yet either. I am lodging bugs against them as well.

Comment 4 by, Sep 28 2015

ashej@ Please acknowledge that feedback has been given. Thanks.

Comment 5 by, Sep 28 2015

Labels: -OS-Mac -Needs-Feedback OS-All

Comment 6 by, Oct 4 2015

 Issue 538806  has been merged into this issue.

Comment 8 by, Feb 10 2016

Status: ExternalDependency

Comment 9 by, Feb 16 2016

Status: Available
Chong, Dave, you're working on InputEvent which is related; are you interested in fixing this?
Components: Blink>Input
Labels: -Pri-4 Hotlist-Input-Dev Pri-2
Including this with chong's work on the `input` event is fine with me (it's probably easy and low risk to change). But it could also belong to the DOM team since they own forms (/cc tkent).

Comment 11 by, Feb 26 2016

Actually, I'm negative of adding new 'input' events, and I don't want to add new 'input' events until other browsers implement them.

All browsers dispatch 'change' and 'input' events synchronously, and these new 'input' events need to be synchronous too.  As you know, synchronous events have made a lot of bugs.

I'd be happy if 'input' and 'change' evens are dispatched asynchronously for these input types.

Firefox 49 now fires these events:
 Issue 799461  has been merged into this issue.
Status: Assigned (was: Available)
Project Member

Comment 16 by, Jan 19 2018

The following revision refers to this bug:

commit 54f8d098b694704893f7abdbba3b1a6ee18ed687
Author: Shanmuga Pandi M <>
Date: Fri Jan 19 06:26:58 2018

Emit "input" event on activation behavior for CheckBox

Intent to implement and ship:!topic/blink-dev/Qc-bOSyU0FQ

Bug:  534245 
Change-Id: Ib97235c26b4b3ccd681e708e232a782d5612745c
Reviewed-by: Kent Tamura <>
Commit-Queue: Shanmuga Pandi <>
Cr-Commit-Position: refs/heads/master@{#530435}

Project Member

Comment 17 by, Jan 30 2018

Comment 18 by, Jan 30 2018

Labels: M-66
Status: Fixed (was: Assigned)

Sign in to add a comment