Ckeditor5: [Safari][IME] Autocorrection changes content after composition in specific cases.

Created on 13 Mar 2017  Â·  4Comments  Â·  Source: ckeditor/ckeditor5

_With Spanish-ISO keyboard (accent under ')_.

Case 1:

  1. <h2>Headin[]g 1</h2>
  2. Press accent
  3. Press esc
  4. Results in <h2>Heading'[]g 1</h2>

Case 2:

  1. <p>Hea[]ding 2</p>
  2. Press accent
  3. Press bold
  4. Type y
  5. Results in <p>He<strong>y</strong>´ding 2</p> and Throws TypeError: null is not an object (evaluating 'viewBlock.parent') in _defaultToModelPosition — mapper.js:222

With auto correct turned off, everything works fine in the above cases.

typing bug

Most helpful comment

Not sure how we should label it in this case? cc @Reinmar

As fixed. Someone fixed it :D

All 4 comments

I couldn't reproduce it but my Safari behaves a bit differently than @f1ames's. On his macOS the word is underlined with blue dotted border. On my with red. This means that some other system kicks in.

It seems it may be more related to autocorrect than IME itself:
feb-27-2018 15-21-15 safari

Also confirming that above scenarios are still reproducible:
feb-27-2018 15-02-31-safari

Ok, I was able to partially reproduce the scenarios shown above (https://github.com/ckeditor/ckeditor5-typing/issues/85#issuecomment-368893835). You have to turn on the autocorrection in Safari:

image

But it behaves a little different than before so I suspect something changed after Safari/macOS update:

  1. <p>Hea[]ding 2</p>.
  2. Delete character before selection (Backspace).
  3. Type a.
  4. Type <.

Hea is replaced with Hey by autocorrect. This is not an issue as no errors are thrown, this is the way autocorrection works. I was not able to reproduce any of two initial scenarios (looks like autocorrection doesn't kicks in that easily while typing inside a word).

heading

I'm closing this issue as it is not reproducible any longer.

_Not sure how we should label it in this case?_ cc @Reinmar

Not sure how we should label it in this case? cc @Reinmar

As fixed. Someone fixed it :D

Was this page helpful?
0 / 5 - 0 ratings