Fix cr-user-autocomplete for Chrome.

appengine/chromium_rietveld/new_static/components/cr-user-autocomplete.html

 <!-- Copyright (c) 2014 The Chromium Authors. All rights reserved.
 Use of this source code is governed by a BSD-style license that can be
 found in the LICENSE file. -->
 
 <link rel="import" href="../common/cr-keyboard.html">
 
 <polymer-element name="cr-user-autocomplete" attributes="value">
     <template>
         <style>
             :host {
@@ skipping 132 matching lines @@
                 var range = this.termRange;
                 var value = user.email.substring(range.text.length) + ", ";
 
                 // Restore selection to where the autocomplete expects it. This prevents the user from
                 // selecting some random text and then clicking a suggestion which might destroy their
                 // input. We might also dismiss the suggestions if the selection moves but there's no
                 // obvious way to detect that.
                 input.selectionStart = range.end;
                 input.selectionEnd = input.selectionStart;
 
-                // For Safari/Chrome:
-                // Simulate the user entering the text. This makes undo work properly instead of using
-                // data binding which is like a big "replace" action.
-                var inputEvent = document.createEvent("TextEvent");
-                if (inputEvent.initTextEvent) {
-                    inputEvent.initTextEvent("textInput", true, true, window, value, 0, "en-US");
-                    input.dispatchEvent(inputEvent);
-                } else if (window.InputEvent) {
-                    // For Firefox we can just update the value and undo will work.
+                // Make sure the input is focused.
+                input.focus();
+
+                // TODO(esprehn): This is a terrible hack but there's no obvious
+                // work around since execCommand doesn't work for input in Firefox
+                // and I can't figure out how to detect that, and we shouldn't
+                // feature detect based on InputEvent otherwise it'll break Chrome
+                // later.
+                if (navigator.userAgent.contains("Firefox")) {

[PhistucK, 2016/08/03 15:51:20]

Yes, no. :P

+                    // For Firefox we can just update the value and undo will work,
+                    // execCommand doesn't seem to update the input value.
                     input.value = input.value.to(input.selectionEnd) + value + input.value.from(input.selectionEnd);
                     input.dispatchEvent(wrap(new InputEvent("input", {
                         data: value,
                         bubbles: true,
                         cancelable:false
                     })));

[PhistucK, 2016/08/03 15:51:20]

Perhaps this is a Blink issue. Have you filed one? :)

+                } else {
+                    // Chrome and Safari can use execCommand.

[Bons, 2016/08/03 15:49:42]

FYI Polymer Rietveld doesn’t render in Safari (mobile or desktop) and hasn’t for
a pretty long time.

[esprehn, 2016/08/03 16:46:53]

It works for me in WebKit nightly , where do you see it not working?

+                    document.execCommand("InsertText", false, value);

[PhistucK, 2016/08/03 15:51:20]

Yes, well, this is non-standard. I advise against it.

[esprehn, 2016/08/03 16:46:53]

Given that there's no workaround we're going to do this. :)

                 }
 
                 // Put the caret back at the end of the new input. This also makes sure the input scrolls
                 // to reveal the new text.
                 input.selectionStart = range.end + value.length;
                 input.selectionEnd = input.selectionStart;
 
                 this.resetAutocomplete();
                 this.didComplete = true;
             },
             resetAutocomplete: function() {
                 this.completions = [];
                 this.termRange = {};
                 this.active = false;
             },
         });
     </script>
 </polymer-element>