Add blink embedder APIs for DomKey conversion.

content/child/blink_platform_impl.cc

Index: content/child/blink_platform_impl.cc
diff --git a/content/child/blink_platform_impl.cc b/content/child/blink_platform_impl.cc
index 57e38bdf315fa26c64bb35712837c92b433ef5e4..1cb71ef6f50745e106e6415b2278b5aace208bce 100644
--- a/content/child/blink_platform_impl.cc
+++ b/content/child/blink_platform_impl.cc
@@ -1374,4 +1374,14 @@ int BlinkPlatformImpl::domEnumFromCodeString(const WebString& code) {
       code.utf8().data()));
 }
 
+WebString BlinkPlatformImpl::domKeyStringFromEnum(int dom_key) {
+  return WebString::fromUTF8(ui::KeycodeConverter::DomKeyToKeyString(
+      static_cast<ui::DomKey>(dom_key)));

[piman, 2015/09/10 18:27:40]

nit: do we need a range check to make sure this static_cast is valid?

[kpschoedel, 2015/09/10 18:41:30]

I can answer this: |ui::DomKey| is explicitly designed to be inter-convertable
with opaque |int| values for Blink's use. Non-opaque accessors for it have
DCHECKs as necessary, and |DomKeyToKeyString()| returns the empty string for
invalid integers (as defined for uninitialized values in the UI Events spec).

+}
+
+int BlinkPlatformImpl::domKeyEnumFromString(const WebString& key_string) {
+  return static_cast<int>(
+      ui::KeycodeConverter::KeyStringToDomKey(key_string.utf8().data()));
+}
+
 }  // namespace content