Bug 1455218 - Add public Etherpad URIs into the blacklist to take back the legacy keypress event behavior r?smaug
Etherpad has some bugs of handling non-printable key events.
https://github.com/ether/etherpad-lite/issues/3383
Unfortunately, Etherpad can be installed into any URI. So, we cannot include
all of the instances into the blacklist but we should add URIs in the list
of Etherpad:
https://github.com/ether/etherpad-lite/wiki/Sites-that-run-Etherpad-Lite
I hope that Nightly testers don't use private Etherpad or non-listed Etherpad.
MozReview-Commit-ID: HSAVwGHhW75
--- a/modules/libpref/init/all.js
+++ b/modules/libpref/init/all.js
@@ -233,17 +233,17 @@ pref("dom.keyboardevent.dispatch_during_
pref("dom.keyboardevent.keypress.dispatch_non_printable_keys_only_system_group_in_content", true);
// Blacklist of domains of web apps which are not aware of strict keypress
// dispatching behavior. This is comma separated list. If you need to match
// all sub-domains, you can specify it as "*.example.com". Additionally, you
// can limit the path. E.g., "example.com/foo" means "example.com/foo*". So,
// if you need to limit under a directory, the path should end with "/" like
// "example.com/foo/". Note that this cannot limit port number for now.
pref("dom.keyboardevent.keypress.hack.dispatch_non_printable_keys",
- "docs.google.com,mail.google.com,hangouts.google.com,keep.google.com");
+ "docs.google.com,mail.google.com,hangouts.google.com,keep.google.com,*.etherpad.org/p/,etherpad.wikimedia.org/p/,board.net/p/,pad.riseup.net/p/,*.sandstorm.io,factor.cc/pad/,*.etherpad.fr/p/,piratenpad.de/p/,notes.typo3.org/p/,etherpad.net/p/,mensuel.framapad.org/p/,pad.ouvaton.coop/,pad.systemli.org/p/,pad.lqdn.fr/p/,public.etherpad-mozilla.org/p/,*.cloudron.me/p/,pad.aquilenet.fr/p/,free.primarypad.com/p/,pad.ondesk.work/p/,demo.maadix.org/etherpad/pads/");
#else
pref("dom.keyboardevent.keypress.dispatch_non_printable_keys_only_system_group_in_content", false);
#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