EventSender needs to assign domKey in the events it generates. I only see domCode getting sent. https://code.google.com/p/chromium/codesearch#chromium/src/components/test_runner/event_sender.cc&sq=package:chromium&l=1528&rcl=1462173394 With the proposed removal of keyIdentifier we need to update the layout tests that are asserting things on keyIdentifier to move them to assert on the DOM Key value.
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/40aff9364e9e84bc98ac26eda1024df88512863e commit 40aff9364e9e84bc98ac26eda1024df88512863e Author: chongz <chongz@chromium.org> Date: Wed May 04 14:30:12 2016 [EventSender] Fill DomKey in synthetic key events With the ship of DomKey and the proposed removal of keyIdentifier we need to be able to updated the layout tests and start using DomKey. BUG= 608351 Review-Url: https://codereview.chromium.org/1948763002 Cr-Commit-Position: refs/heads/master@{#391503} [modify] https://crrev.com/40aff9364e9e84bc98ac26eda1024df88512863e/components/test_runner/event_sender.cc [delete] https://crrev.com/8b8866014d743f8ee4fd9a5229f7ec28334b46b7/third_party/WebKit/LayoutTests/fast/events/keyboardevent-key-expected.txt [modify] https://crrev.com/40aff9364e9e84bc98ac26eda1024df88512863e/third_party/WebKit/LayoutTests/fast/events/keyboardevent-key.html [delete] https://crrev.com/8b8866014d743f8ee4fd9a5229f7ec28334b46b7/third_party/WebKit/LayoutTests/virtual/pointerevent/fast/events/keyboardevent-key-expected.txt [delete] https://crrev.com/8b8866014d743f8ee4fd9a5229f7ec28334b46b7/third_party/WebKit/LayoutTests/virtual/trustedeventsdefaultaction/fast/events/keyboardevent-key-expected.txt
Comment 1 by chongz@chromium.org
, May 3 2016