Bug 1430551 - Make editor use <div> as defaultParagraphSeparator even in release channel r?m_kato
No Nightly testers don't report new compatibility issue. Additionally, if we
make Firefox use <div> as defaultParagraphSeparator in release build, web
services may stop supporting our current behavior quickly because they can
get rid of hack for us. Therefore, we should do this in the cycle of Gecko 60
which is next ESR. If we did this later, ESR users may have become not to be
able to use existing web services suddenly immediately after we did this in 61
or 62. We should avoid this bad scenario.
MozReview-Commit-ID: 7Um79Ky7n8i
--- a/modules/libpref/init/all.js
+++ b/modules/libpref/init/all.js
@@ -1258,21 +1258,17 @@ pref("extensions.spellcheck.inline.max-m
// belong in comm-central/editor/ui/composer.js
pref("editor.use_custom_colors", false);
pref("editor.singleLine.pasteNewlines", 2);
pref("editor.use_css", false);
pref("editor.css.default_length_unit", "px");
pref("editor.resizing.preserve_ratio", true);
pref("editor.positioning.offset", 0);
-#ifdef EARLY_BETA_OR_EARLIER
pref("editor.use_div_for_default_newlines", true);
-#else
-pref("editor.use_div_for_default_newlines", false);
-#endif
// Scripts & Windows prefs
pref("dom.disable_beforeunload", false);
pref("dom.disable_window_flip", false);
pref("dom.disable_window_move_resize", false);
pref("dom.disable_window_open_feature.titlebar", false);
pref("dom.disable_window_open_feature.close", false);