Bug 1510081 - Remove docs.google.com from "dom.keyboardevent.keypress.hack.use_legacy_keycode_and_charcode" r=smaug
authorMasayuki Nakano <masayuki@d-toybox.com>
Tue, 27 Nov 2018 13:10:31 +0000
changeset 507481 ce0cebad842b1fc3c14b552dccaa59dc9ec8dd09
parent 507480 cda49d66b3ccef746f0f077b80173cf0ae3a2899
child 507482 f58c9289f62e89f87c1899b9b7b89dda191d740a
push id1905
push userffxbld-merge
push dateMon, 21 Jan 2019 12:33:13 +0000
treeherdermozilla-release@c2fca1944d8c [default view] [failures only]
perfherder[talos] [build metrics] [platform microbench] (compared to previous push)
reviewerssmaug
bugs1510081
milestone65.0a1
first release with
nightly linux32
nightly linux64
nightly mac
nightly win32
nightly win64
last release without
nightly linux32
nightly linux64
nightly mac
nightly win32
nightly win64
Bug 1510081 - Remove docs.google.com from "dom.keyboardevent.keypress.hack.use_legacy_keycode_and_charcode" r=smaug It seems that Google Docs have already been fixed their bugs of mirroring keyCode and charCode values of our keypress events. Therefore, we should remove docs.google.com from the blacklist and collect new feedback from Nightly testers. Differential Revision: https://phabricator.services.mozilla.com/D13035
modules/libpref/init/all.js
--- a/modules/libpref/init/all.js
+++ b/modules/libpref/init/all.js
@@ -235,17 +235,17 @@ pref("dom.keyboardevent.keypress.dispatc
 
 #ifdef NIGHTLY_BUILD
 // Blacklist of domains of web apps which handle keyCode and charCode of
 // keypress events with a path only for Firefox (i.e., broken if we set
 // non-zero keyCode or charCode value to the other).  The format is exactly
 // same as "dom.keyboardevent.keypress.hack.dispatch_non_printable_keys". So,
 // check its explanation for the detail.
 pref("dom.keyboardevent.keypress.hack.use_legacy_keycode_and_charcode",
-     "docs.google.com,www.rememberthemilk.com");
+     "www.rememberthemilk.com");
 #endif
 
 // Whether the WebMIDI API is enabled
 pref("dom.webmidi.enabled", false);
 
 // Whether to enable the JavaScript start-up cache. This causes one of the first
 // execution to record the bytecode of the JavaScript function used, and save it
 // in the existing cache entry. On the following loads of the same script, the