In Chrome SPAN tags appear when merging paragraphs with delete/backspace.

[lmeurs]

Occurs in Chrome v24.0.1312.56 / CKEditor 4.0.1 (revision d02739b) / CKEditor 4 DEV (Standard) (revision d02739b) (nightly build demo)

Did not occur in Firefox v17.0.1

When you have a paragraph with several lines of text, ie.:

<p>line1<br />
line2</p>

and want to create 2 separate paragraphs, you could go with your cursor to the end of line1, press ENTER to create a new paragraph and press DELETE to remove the whiteline caused by the BR tag. Then CKEditor puts some HTML in a SPAN tag with a line-height styling.

<p>line1</p>
<p><span style="line-height: 1.6em;">line2</span></p>

Other examples: It also happens when trying to create a single line out of the next cases:

<p><br />
line2</p>

and

<p>line1</p>
<p>line2</p>

Edits

• This happens when two paragraphs are joined with delete. Tag br has nothing to do here.

• Another TC: ​http://stackoverflow.com/questions/14952515/ckeditor-entermode-issue-in-chrome

Content: <h1>^test</h1> + enter + backspace creates awful mess.

• Browser issues:
  • ​http://code.google.com/p/chromium/issues/detail?id=226941
  • ​https://bugs.webkit.org/show_bug.cgi?id=114791

• Related issues: #8438, #8439, #8440, #10359.

[Jakub Ś]

Problem can be reproduced from CKEditor 4.0 in Chrome only.

[Jakub Ś]

#10056 was marked as duplicate.

[Jakub Ś]

#10064 was marked as duplicate.

[mandius]

Adding as CC

[Piotrek Koszuliński]

I started to feel that we can't rely on Webkit's backspace behaviour any more. Those styling spans are unacceptable thus I'm changing priority to high.

[Frederico Caldeira Knabben]

To start off, we need a ticket opened at WebKit's side. Considering that this is an annoying browser bug, there is a chance that they'll be interested on having this fixed.

[mandius]

This appears to be fixed in Chrome 25.0.1364.97 m on Windows!

[lmeurs]

Unfortunately the problem still occurs on my Chrome 25.0.1364.97 on Windows.

[Piotrek Koszuliński]

Thanks for info.

We'll take care of this issue as soon as we'll close 4.1 and 4.0.2 releases.

[Jakub Ś]

#10133 was marked as duplicate.

[mandius]

Replying to lmeurs:

Unfortunately the problem still occurs on my Chrome 25.0.1364.97 on Windows.

Hmmm. I just tried again and you're right, it is still doing it! I got excited because I tested on my site's CKeditor this morning and then in the demo and it didn't do it in either. I've just closed and reopened Chrome and now it's doing it again. WTF? Sorry for the false hope! :(

[Roman]

Hi guys!

Any updates? Just updated to 4.1, but unfortunately the problem is still exist. Chrome 25.0.1364.172 Hope you be able to fix/help soon.

Thank you!

[Piotrek Koszuliński]

We're focused on other tasks right now and we won't work on bringing the sanity to how backspace/del works on Chrome at least for few weeks, because this is pretty tough task. In fact, we will first report this issue on Webkit's bug track, to see if this is intentional behaviour or not. I guess that I'll have some time to handle this next week.

[Roman]

Hi Reinmar,

Thanks for quick response. That's sad, but I still hoping =) I also niticed that new CKEditor 4.1 has new events, toHtml and toDataFormat. Maybe I can filter this bug, could you please point out the right direction to me?

[Matti Järvinen]

following cc

[ivanjh]

Also affects 26.0.1410.43 (Win & Mac)

[Berry]

Experiencing the same issue, following cc

[Jakub Ś]

replying to comment:17 minkinroman@... neither these events nor ACF seem to be any help here.

The only way to get rid of this bug is by implementing custom del/backspace (non-trivial). Another would be fixing this by Chrome.

[Chris]

Also experiencing on Ubuntu Chromium 25.0.1364.160

[Piotrek Koszuliński]

​http://code.google.com/p/chromium/issues/detail?id=226941

I reported this issue on Chromium bug tracker, which is now also used for Blink engine.

Let's see what Chrome developers will say.

[ryanissamson]

Whew, glad it wasn't just me. Yea - this is happening still - OS X Chromium 26.0.1410.43

[jcisio]

This is really annoying. I've just pumping on the Chrome issue with detail on a WebKit commit ​https://trac.webkit.org/changeset/135421.

However, the easiest way to fix it, now, is to remove content.css.

[Piotrek Koszuliński]

Thanks for your help. I'll report the same ticket on Webkit bugtracker too.

[crisward]

This seems to fix it for me. Uses a bit of Jquery, but doesn't need it. Not ideal I know, but it works.

var editor = CKEDITOR.inline("editor",options);

$("#editor").on('keyup',function(e){
        if(e.keyCode===8){
          var node=editor.getSelection().getRanges()[0].endContainer.$.nextSibling;
          if (node.tagName === "SPAN"){
            $(node).replaceWith($(node).contents());
          }
        }
});

[ryanissamson]

I removed the content.css file and that fixed the issue. Hopefully it gets sorted soon!

[Jakub Ś]

@ryanissamson thanks for the tip. It seems if you remove below CSS class with line-height: 1.6em; you don't get this problem anymore.

.cke_editable
{
	font-size: 13px;
	line-height: 1.6em;
}

I have also checked the same in plain contenteditable element without CKEditor. Result is the same. This is definitely Browser Bug.

[jcisio]

A bug, or maybe a feature, as the link I posted in ​http://dev.ckeditor.com/ticket/9998#comment:25

[Matti Järvinen]

Would it be feasible to compare inline style CSS against editor CSS with Chrome as a temporary fix for the browser until Webkit issue is resolved?

[Piotrek Koszuliński]

Most likely it was meant to be a feature, but it is very unwelcome feature. Webkit is just trying to do too much - it may look well (although I'm not sure about that), but the markup is corrupted. In the ​Blink/Webkit bug report I described other behaviours which seem to be related - all them pay too much attention to visual aspect of editing, but not to markup and API, so the result is ridiculous.

And yes, removing all styles from contents.css will help for some of these issues in framed editor. You may check the file attached to bug report - I also needed to apply some styling to trigger these "features". However, this is not going to help in inline editing, where it's normal that many styles are applied to the content and it does not prevent from element transformation.

Would it be feasible to compare inline style CSS against editor CSS with Chrome as a temporary fix for the browser until Webkit issue is resolved?

I'm not sure if I understand, but I think that you mean something similar to what Webkit is trying to do (but in the reverse way). And this definitely is not feasible (Webkit is good example of that :D).

If we're going to fix this, we'll try handling backspace completely manually. It is the only reasonable way, although it is also very complicated. Thus, first I'd like to have some feedback from Webkit/Blink's devs.

[Piotrek Koszuliński]

I created a bug report also on Webkit bug tracker: ​https://bugs.webkit.org/show_bug.cgi?id=114791

[Olek Nowodziński]

Another possibly related ticket #10359.