492678 - Changes to value attribute on buttons should fire EVENT_NAME_CHANGE

Status: NEW

(Core :: Disability Access APIs, defect)

Description

[David Bolter [:davidb] (NeedInfo me for attention)]

Because with <input type="button" value="foo"> foo is the accessible name, when the value is changed we should really fire EVENT_NAME_CHANGE, instead of EVENT_VALUE_CHANGE.

Comment 1

[David Bolter [:davidb] (NeedInfo me for attention)]

Attachment: background - IRC chat

Comment 2

[alexander :surkov (:asurkov)]

David, it's very specific case and we fire another events so NVDA buffer is updated correctly like Jamie said. We can't fire name change event for everything because of performance so I'm not sure we want to fix this.

Comment 3

[Marco Zehe (:MarcoZ)]

But we should perhaps get rid of that bogus valuechange, right?

Comment 4

[David Bolter [:davidb] (NeedInfo me for attention)]

It is really a rare case. I'm fine with closing this as WONTFIX... just wanted to capture it for discussion.

Marco, good point but I think the bogus valuechange could actually be better than nothing. Savvy AT could conceivably use that to catch button renaming... and adding code to not fire the event is probably more noise than value.

Comment 5

[alexander :surkov (:asurkov)]

I don't think we fire value change event. Are you sure?

Comment 6

[Marco Zehe (:MarcoZ)]

Still valid in 10.0a1.