Ckeditor4: [Chrome]   is inserted instead of space

Created on 27 Jan 2020  Â·  10Comments  Â·  Source: ckeditor/ckeditor4

Type of report

Bug

Provide detailed reproduction steps (if any)

  1. Type a space between two words somewhere in the middle of a sentence:
    <h1>Hello| world!</h1> -> <h1>Hello | world!</h1> - the caret becomes between two spaces.
  2. Press backspace to delete one space on the left.
  3. Type a space and new word "foobar".

Expected result

<h1>Hello foobar world!</h1>

Actual result

<h1>Hello foobar&nbsp;world!</h1>

Other details

It doesn't reproduce in FF.
It doesn't reproduce in Chrome in a raw <div contenteditable>.
This bug is almost the same as https://dev.ckeditor.com/ticket/11415, but reproduction steps are different.

chrome edge safari L confirmed bug

Most helpful comment

any update on this bug?

All 10 comments

any update on this bug?

any update on this bug?

I wonder what is the impact of this issue, @nag5000 could you elaborate on the problems it causes for you?

Any input from other people upvoting this issue is more than welcome too. It will help us to understand better what are the cases here and what will be the best solution (and what parts of the editing/outputing process it should involve).

@f1ames Writing blog posts, leaving comments... almost any case where ckeditor can be used. If the output is html with a lot of non-breaking spaces, it will not be rendered correctly to the end-user.

Any update on this issue?

I faced this issue intermittently when updating lengthy content. Backspace and space keys are used frequently. Because of &nbsp; the line breaks. It is difficult to solve if source button is disabled.

Is this related to https://www.drupal.org/project/ckeditor_details/issues/3159925?

For now, I see that:

  1. Putting extra space before existing space gives us &nbsp;space combination for Chrome and FF.
  2. Visually we have caret between two spaces.
  3. When we delete first or second visual spaces (backspace or delete):

    • for chrome gives us only &nbsp;

    • for FF gives us space

The same for wysiwygarea and divarea

Also bugged in IE11 - However, it works that way even in plain contenteditable - without CKEditor.

Was this page helpful?
0 / 5 - 0 ratings