- From: Ryosuke Niwa <rniwa@apple.com>
- Date: Fri, 04 Nov 2016 22:00:19 -0700
- To: Grisha Lyukshin <glyuk@microsoft.com>
- Cc: public-editing-tf <public-editing-tf@w3.org>, Anupam Snigdha <snianu@microsoft.com>
- Message-id: <05ABCDA9-E26A-49B1-B563-FA3FF636071A@apple.com>
> On Sep 29, 2016, at 5:47 PM, Grisha Lyukshin <glyuk@microsoft.com> wrote: > > Hello Editing Task Force, > > I wanted to run the following scenario by you and hear your stance on it? > > Here is the use case code snippet: > > <body contenteditable="true"> > <div><span style="color:red;">a</span></div> > <div><span style="color:blue;">bc</span></div> > </body> > > Jsfiddle: https://jsfiddle.net/whbk8npa/ <https://jsfiddle.net/whbk8npa/> > > this markup will be displayed to the user like > a > bc > > 1. Place a caret to the right of character 'a' > 2. Hit delete (new line will be removed and user will see 'abc' > 3. Hit delete again and user will see 'ac' > 4. Type some character, 'z' for example. User will see different results, depending on the browser: > > Chrome > Edge > Firefox > Safari > azc > azc > azc > Didn't test - someone who has Safari, please test Safari’s behavior matches that of Chrome & Edge here. > Now, repeat the experiment but this time, delete everything to the right of 'a' so the end result would look like so 'a'. Results are again, quite different. Are you deleting text by forward delete (i.e. pressing the Delete key on physical keyboard) to do this? If so, Safari’s behavior matches that of Chrome. > > Chrome > Edge > Firefox > Safari > az > az > az > Didn't test - someone who has Safari, please test > > In this case, Chrome seems to grabs the style from the span to the right of 'a' if the last character in the span has been removed. > Edge still grabs styles from the span that is to the left of 'a'. > Firefox seems to do its own thing. > > What do you think the most sensible behavior here is? Assuming we’re using delete key on Windows and forward delete on Mac, Chrome & Safari’s behavior matches that of NSTextView on Mac, and it’s kind of expected. Our behavior in the first case doesn’t match NSTextView so that’s more of a bug as far as we’re concerned. - R. Niwa
Received on Saturday, 5 November 2016 05:00:54 UTC