This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 21377 - onchange event on input type=range is handled differently across browsers: https://bugzilla.mozilla.org/show_bug.cgi?id=853670
Summary: onchange event on input type=range is handled differently across browsers: ht...
Status: RESOLVED FIXED
Alias: None
Product: WHATWG
Classification: Unclassified
Component: HTML (show other bugs)
Version: unspecified
Hardware: Other other
: P3 normal
Target Milestone: Unsorted
Assignee: Ian 'Hixie' Hickson
QA Contact: contributor
URL: http://www.whatwg.org/specs/web-apps/...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-03-22 19:02 UTC by contributor
Modified: 2013-04-01 18:20 UTC (History)
3 users (show)

See Also:

Attachments

Description contributor 2013-03-22 19:02:21 UTC 
Specification: http://www.whatwg.org/specs/web-apps/current-work/multipage/common-input-element-attributes.html
Multipage: http://www.whatwg.org/C#common-input-element-apis
Complete: http://www.whatwg.org/c#common-input-element-apis

Comment:
onchange event on input type=range is handled differently across browsers:
https://bugzilla.mozilla.org/show_bug.cgi?id=853670

Posted from: 91.114.135.34
User agent: Mozilla/5.0 (X11; Linux x86_64; rv:22.0) Gecko/20130322 Firefox/22.0
Comment 1 Ian 'Hixie' Hickson 2013-04-01 18:20:10 UTC 
Thanks. I've added an example of what the spec means that should clarify to Chrome and IE that their implementation is wrong.
Comment 2 contributor 2013-04-01 18:20:14 UTC 
Checked in as WHATWG revision r7787.
Check-in comment: Clarify this to make it clear that Chrome and IE's behaviours are wrong with <input type=range onchange>.
http://html5.org/tools/web-apps-tracker?from=7786&to=7787