25603 2014-05-08 12:23:28 +0000 key value "MediaTrack(Next|Previous)" vs. code value "Media(Next|Previous)Track" 2014-05-13 00:08:24 +0000 1 1 1 Unclassified WebAppsWG HISTORICAL - DOM3 Events unspecified PC Windows NT RESOLVED FIXED P2 normal --- 1 masayuki travil garykac mike travil www-dom public-webapps-bugzilla oldest_to_newest 105430 0 masayuki 2014-05-08 12:23:28 +0000 This is similar to bug 25373 and bug 25601. Current code value, Media(Next|Previous)Track are same as older draft's key names. Therefore, I think .key value table should be rolled back. Then, IE9 and current Firefox become compatible with D3E draft's key names again. 105431 1 masayuki 2014-05-08 12:24:12 +0000 Oops, this must be Garykac's issue. 105591 2 travil 2014-05-09 21:37:45 +0000 I like aligning these with existing implementations :) I'll go ahead and make the change. Yell at me if you want me to change the code values to match the key values instead... 105595 3 travil 2014-05-09 21:42:31 +0000 I've done this now: https://dvcs.w3.org/hg/dom3events/rev/705e5c8af455 105597 4 garykac 2014-05-09 21:46:07 +0000 They are named that way to be consistent with all the other key names. Namely, related keys share the same prefix so that they are easy to find. So we don't have "FastForwardMedia" and "RewindMedia" but rather "MediaFastForward" and "MediaRewind" The naming consistency may be a change from the hodge-podge naming that the keys had earlier. But the renaming mostly affected rarely used keys (like the media ones). 105599 5 travil 2014-05-09 21:48:29 +0000 So you'd like to see the change applied in reverse?