[InputEvent] Allow transpose and yank in plain-text field

third_party/WebKit/Source/core/editing/commands/CompositeEditCommand.cpp

Index: third_party/WebKit/Source/core/editing/commands/CompositeEditCommand.cpp
diff --git a/third_party/WebKit/Source/core/editing/commands/CompositeEditCommand.cpp b/third_party/WebKit/Source/core/editing/commands/CompositeEditCommand.cpp
index 012a9693251f32f8d429ad6c62433ff70c5ff4e7..ec63558e4d4fb527ce51f90e25a72a682be932bc 100644
--- a/third_party/WebKit/Source/core/editing/commands/CompositeEditCommand.cpp
+++ b/third_party/WebKit/Source/core/editing/commands/CompositeEditCommand.cpp
@@ -100,6 +100,8 @@ bool CompositeEditCommand::apply() {
       case InputEvent::InputType::InsertParagraph:
       case InputEvent::InputType::InsertFromPaste:
       case InputEvent::InputType::InsertFromDrop:
+      case InputEvent::InputType::InsertFromYank:

[yosin_UTC9, 2017/03/24 01:26:48]

BTW, Do we really need to have this switch-statement?
We have queryCommandEnabled(commandName) to do this.
Thus, we have two different places for checking command enablility.

[chongz, 2017/03/24 14:57:20]

This pattern was originated from WebKit, see:
https://chromium.googlesource.com/chromium/src/+blame/07a33c8ce604eeec637abe0...

But yes I think we can get rid of this as |queryCommandEnabled(commandName)| is
doing the same thing.

+      case InputEvent::InputType::InsertTranspose:
       case InputEvent::InputType::InsertReplacementText:
       case InputEvent::InputType::InsertCompositionText:
       case InputEvent::InputType::DeleteWordBackward:
@@ -113,7 +115,8 @@ bool CompositeEditCommand::apply() {
       case InputEvent::InputType::None:
         break;
       default:
-        NOTREACHED();
+        NOTREACHED() << "Not supported input type on plain-text only element:"
+                     << static_cast<int>(inputType());
         return false;
     }
   }