Re: Intent to enable as default paragraph separator of contenteditable/designMode editor by default
On 2/15/2018 5:40 AM, Jet Villegas wrote:
SGTM. Please follow up to make sure this workaround makes it on to MDN:
document.execCommand("defaultParagraphSeparator", false, "br");
Thx!
Hi, Jet-san, I updated the document in MDN:
https://developer.mozilla.org/en-US/docs/Web/Guide/HTML/Editable_content#Differences_in_markup_generation
--
Masayuki Nakano
Software Engineer, Mozilla
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
Re: Intent to enable as default paragraph separator of contenteditable/designMode editor by default
SGTM. Please follow up to make sure this workaround makes it on to MDN:
> document.execCommand("defaultParagraphSeparator", false, "br");
Thx!
On Tue, Feb 13, 2018 at 8:14 PM, Masayuki Nakano
wrote:
> Starting from Firefox 60, I'd like to enable as default paragraph
> separator of contenteditable/designMode editor by default even in release
> channel.
>
> When user typing Enter key in editing host (or body in designMode),
> Firefox 59 and earlier insert element. However, the other browsers
> insert element (and wraps current line with too). This is
> declared by execCommand spec (Unofficial draft):
> https://w3c.github.io/editing/execCommand.html#the-insertparagraph-command
>
> We've already enabled this behavior on Nightly and Early Beta since
> Firefox 55:
> https://bugzilla.mozilla.org/show_bug.cgi?id=1297414
>
> And now, we don't have confirmed regression reports which we haven't
> worked on. Additionally, once we use same behavior with the other browsers
> in this major difference, new web services could becomes not supporting our
> current behavior. That means ESR users may become not to be able to use
> such web services. Therefore, I'd like to enable this before shipping ESR
> 60.
>
> The bug is:
> https://bugzilla.mozilla.org/show_bug.cgi?id=1430551
>
> Note that even if some web services have trouble with new our behavior,
> they can take the old behavior with inserting this line:
>
> document.execCommand("defaultParagraphSeparator", false, "br");
>
> --
> Masayuki Nakano
> Software Engineer, Mozilla
> ___
> dev-platform mailing list
> dev-platform@lists.mozilla.org
> https://lists.mozilla.org/listinfo/dev-platform
>
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
Intent to enable as default paragraph separator of contenteditable/designMode editor by default
Starting from Firefox 60, I'd like to enable as default paragraph
separator of contenteditable/designMode editor by default even in
release channel.
When user typing Enter key in editing host (or body in designMode),
Firefox 59 and earlier insert element. However, the other browsers
insert element (and wraps current line with too). This is
declared by execCommand spec (Unofficial draft):
https://w3c.github.io/editing/execCommand.html#the-insertparagraph-command
We've already enabled this behavior on Nightly and Early Beta since
Firefox 55:
https://bugzilla.mozilla.org/show_bug.cgi?id=1297414
And now, we don't have confirmed regression reports which we haven't
worked on. Additionally, once we use same behavior with the other
browsers in this major difference, new web services could becomes not
supporting our current behavior. That means ESR users may become not to
be able to use such web services. Therefore, I'd like to enable this
before shipping ESR 60.
The bug is:
https://bugzilla.mozilla.org/show_bug.cgi?id=1430551
Note that even if some web services have trouble with new our behavior,
they can take the old behavior with inserting this line:
document.execCommand("defaultParagraphSeparator", false, "br");
--
Masayuki Nakano
Software Engineer, Mozilla
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
