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 17755 - IE9 uses different key names for "AudioMute", "AudioVolumeDown" and "AudioVolumeUp"
Summary: IE9 uses different key names for "AudioMute", "AudioVolumeDown" and "AudioVol...
Status: RESOLVED FIXED
Alias: None
Product: WebAppsWG
Classification: Unclassified
Component: HISTORICAL - DOM3 Events (show other bugs)
Version: unspecified
Hardware: PC Windows NT
: P2 normal
Target Milestone: ---
Assignee: Travis Leithead [MSFT]
QA Contact: public-webapps-bugzilla
URL:
Whiteboard:
Keywords: needsReview
Depends on:
Blocks:
 
Reported: 2012-07-12 07:53 UTC by Masayuki Nakano
Modified: 2012-08-23 22:01 UTC (History)
4 users (show)

See Also:

Attachments

Description Masayuki Nakano 2012-07-12 07:53:02 UTC 
I'd like to confirm if D3E spec uses IE9's key name or not.

D3E spec defines "AudioMute", "AudioVolumeDown" and "AudioVolumeUp".

However, IE9 users "VolumeMute", "VolumeDown" and "VolumeUp".

D3E spec defines other "Audio" prefixed key names. So, it may make sense to add "Audio" prefix for all of them. However, it sounds like a little bit redundant for me. I mean, "Volume" prefixed keys sounds like audio related for me.

For compatibility with IE9, it's better to change D3E spec's key names, but I'm not sure which is better way for these keys.
Comment 1 Travis Leithead [MSFT] 2012-08-23 22:01:16 UTC 
The VolumeMute, VolumeDown, and VolumeUp make sense for alignment. I tried standardizing on Volume for the other key names, but it just didn't seem right, for example:

VolumeBassBoostUp just didn't seem as descriptively accurate as AudioBassBoostUp (because the subject is the "bass boost" not the Up, and volume bass boost doesn't make sense to me.

Fixed in the latest version of the spec: r240

http://dev.w3.org/2006/webapi/DOM-Level-3-Events/html/DOM3-Events.html?rev=1.240