Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[IME][Windows][Chrome] Turning bold on/off during composition breaks it #976

Closed
f1ames opened this issue Apr 18, 2018 · 1 comment
Closed
Labels
browser:chrome package:typing type:bug This issue reports a buggy (incorrect) behavior.

Comments

@f1ames
Copy link
Contributor

f1ames commented Apr 18, 2018

Is this a bug report or feature request? (choose one)

🐞 Bug report

💻 Version of CKEditor

Tested on v1.0.0-beta.2.

📋 Steps to reproduce

Extracted from ckeditor/ckeditor5-engine#1355 (comment).

  1. Open the article sample.
  2. Put the caret at the end of the Paragraph.
  3. Press Ctrl + B.
  4. Start the composition (Hiragana) and type something.
  5. Press Ctrl + B.

✅ Expected result

Well, not sure what should exactly happen. On native contenteditable the composition is just continued (as one part), however if you start switching composed characters (Arrow up or Arrow down) the whole composition becomes bolded. It might be hard to mimic such behaviour.

Maybe we should just disallow turning bold off during composition? Not sure how it will affect usability for the users which create content mainly by composing.

❎ Actual result

Composition is broken, continuing typing after second Ctrl + B press reinsert whole composed part (so it is duplicated) - the good news is composition still works so you can end it and delete duplicated part.

📃 Other details that might be useful

Only on Chrome on Windows it is possible to turn off styling (e.g. Bold) during composition.

@Mgsy
Copy link
Member

Mgsy commented Sep 2, 2019

I can't reproduce it anymore.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
browser:chrome package:typing type:bug This issue reports a buggy (incorrect) behavior.
Projects
None yet
Development

No branches or pull requests

2 participants