Fire change event when HTMLRangeAccessible::SetCurValue is called
Categories
(Core :: Disability Access APIs, defect)
Tracking
()
People
(Reporter: Jamie, Unassigned)
References
(Blocks 1 open bug)
Details
Inspired by this WebKit change twisniewski brought to my attention:
https://github.com/WebKit/WebKit/commit/87dc85177fd870edf465c6a24ee4ed79d9f56bdf
https://bugs.webkit.org/show_bug.cgi?id=233449
It looks like we might have the reverse bug to the one WebKit did, where we fire an input event but not a change event.
Simple test case:
data:text/html,<input type="range" onchange="alert('change');" oninput="alert('input');">
When calling SetCurValue (e.g. via VoiceOver increment/decrement or IAccessibleValue::SetCurrentValue), we should see both alerts. I only see "input".
I'm honestly not sure what the spec says about the change event and whether we're required to fire it in this case. A brief look isn't turning it up, so we'll need to determine that first.
Description
•