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

CKEditor 5: One-click-correction stopped working with 35.3.0 #7427

Closed
TobiasHartlehnert opened this issue Nov 15, 2022 · 1 comment
Closed
Assignees

Comments

@TobiasHartlehnert
Copy link

TobiasHartlehnert commented Nov 15, 2022

Due to refactoring of some core aspects of CKEditor 5, the one-click-correction of LanguageTool stopped working starting with version 35.3.0, released on 2022-11-02.

Reproduction steps

  1. Navigate to Classic Editor example
  2. Click inside the editing area; LanguageTool will underline "earth" in first paragraph as a possible error
  3. Click anywhere inside "earth" to open the LanguageTool correction box
  4. Click on the suggested correction "earth," (blue button)

✔️ Expected result

"earth" should change to "earth,"

❌ Actual result

Text is not changed. JS error is thrown, see Console (Chrome: "Uncaught TypeError: Cannot read properties of null (reading 'root') ...", Firefox: "Uncaught CKEditorError: i is null ...").

📃 Other details

  • Browser: Chrome 107.0.5304.106, Firefox 106.0.5
  • OS: Windows 10 Pro

I already opened an issue @ ckeditor5 repo, and the team acknowledged the issue as a result of the beforeInput refactoring that came with 35.3.0:

It looks like this browser extension is using beforeInput:insertText but it is not providing targetRanges this might be easy to fix by enabling fallback to the DOM document selection.

It would be nice if you can fix this on your end, instead of having CKEditor implement a workaround, as Reinmar suggested.

@tiff
Copy link
Member

tiff commented Nov 16, 2022

Thanks for bringing this to our attention. We will begin rolling out a fix for this, beginning of next week.

@tiff tiff closed this as completed Nov 16, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants