Bug 1343451 - part 1: Declare (DOM|NS)_VK_PROCESSKEY for keyCode value during composition r=smaug

When native key event is handled by IME, we should set keyCode to 0xE5 (229,
VK_PROCESS of virtual keycode of Windows) for behaving same as the other
browsers.

This patch declares it same as other keyCode values.

MozReview-Commit-ID: 666bB1qOEgv

--HG--
extra : rebase_source : 8edcc49aab537240fb696b010e642848a6d439d4

dom/events/VirtualKeyCodeList.h

@@ -212,6 +212,9 @@ DEFINE_VK_INTERNAL(_ALTGR)
 
 DEFINE_VK_INTERNAL(_WIN_ICO_HELP)
 DEFINE_VK_INTERNAL(_WIN_ICO_00)
+
+DEFINE_VK_INTERNAL(_PROCESSKEY)
+
 DEFINE_VK_INTERNAL(_WIN_ICO_CLEAR)
 DEFINE_VK_INTERNAL(_WIN_OEM_RESET)
 DEFINE_VK_INTERNAL(_WIN_OEM_JUMP)

dom/webidl/KeyEvent.webidl

@@ -195,6 +195,12 @@ interface KeyEvent
   // for compatibility with the other web browsers on Windows.
   const unsigned long DOM_VK_WIN_ICO_HELP    = 0xE3;
   const unsigned long DOM_VK_WIN_ICO_00      = 0xE4;
+
+  // IME processed key.
+  const unsigned long DOM_VK_PROCESSKEY      = 0xE5;
+
+  // OEM specific virtual keyCode of Windows should pass through DOM keyCode
+  // for compatibility with the other web browsers on Windows.
   const unsigned long DOM_VK_WIN_ICO_CLEAR   = 0xE6;
   const unsigned long DOM_VK_WIN_OEM_RESET   = 0xE9;
   const unsigned long DOM_VK_WIN_OEM_JUMP    = 0xEA;