Re: Intent to disable (hide) Gecko specific editing UI of HTML editor by default

We put off to change this until we get enough telemetry data. Now, we have a lot of data in Beta 62 users. That indicates that each specific UI is rarely shown (< 0.5% of all HTMLEditor instances). However, according to operation count per HTMLEditor instance, some of them may be used by

Re: Intent to disable (hide) Gecko specific editing UI of HTML editor by default

Hi Masayuki, First of all, thank you for taking on this task. I have a few questions. * What does the backwards compatibility story for these changes look like? Would we end up for example throwing exceptions or returning a different value from execCommand/queryCommandState/etc for one of the

Re: Intent to disable (hide) Gecko specific editing UI of HTML editor by default

On Thu, Apr 5, 2018 at 11:08 PM Masayuki Nakano wrote: > On 4/6/2018 2:50 AM, Ehsan Akhgari wrote: > > Hi Masayuki, > > > > First of all, thank you for taking on this task. I have a few questions. > > > > * What does the backwards compatibility story for these changes

Re: Intent to disable (hide) Gecko specific editing UI of HTML editor by default

> * Add new command "enableAbsolutePositionEditing" command for allowing to enable #4 There is no way to use absolute position editing on Firefox because cmd_abspos is used by comm-central only. So I guess that it might be unnecessary to add this command for Firefox and is better to add a

Re: Intent to disable (hide) Gecko specific editing UI of HTML editor by default

On 4/7/2018 12:39 AM, Ehsan Akhgari wrote: On Thu, Apr 5, 2018 at 11:08 PM Masayuki Nakano > wrote: On 4/6/2018 2:50 AM, Ehsan Akhgari wrote: > Hi Masayuki, > > First of all, thank you for taking on this task.  I have a few

Re: Intent to disable (hide) Gecko specific editing UI of HTML editor by default

On 4/6/2018 2:50 AM, Ehsan Akhgari wrote: Hi Masayuki, First of all, thank you for taking on this task.  I have a few questions. * What does the backwards compatibility story for these changes look like?  Would we end up for example throwing exceptions or returning a different value from

Re: Intent to disable (hide) Gecko specific editing UI of HTML editor by default

On 4/6/2018 9:25 AM, Makoto Kato wrote: > * Add new command "enableAbsolutePositionEditing" command for allowing to enable #4 There is no way to use absolute position editing on Firefox because cmd_abspos is used by comm-central only.  So I guess that it might be unnecessary to add this

Intent to disable (hide) Gecko specific editing UI of HTML editor by default

This incompatibility is pointed by W3C's Editing API WG: https://github.com/w3c/editing/issues/171 Gecko has some specific editing UI of HTML editor. 1. Resiziers of , , absolute positioned elements. 2. Adding new table row/column from buttons. 3. Removing existing table row/column from buttons.