Editor does not style blanks at end of line




6 years ago
2 years ago


(Reporter: cacyclewp, Unassigned)


29 Branch
Windows XP

Firefox Tracking Flags

(Not tracked)



(2 attachments)



6 years ago
Posted file Testcase
User Agent: Mozilla/5.0 (Windows NT 5.1; rv:24.0) Gecko/20100101 Firefox/24.0 (Beta/Release)
Build ID: 20130910160258

Steps to reproduce:

1) The editor is active (e.g. iframe in designmode or contenteditable).
2) A span contains blanks before a line break (either added by editing or in the original content) 
3) The span has styling such as background color

Actual results:

The trailing spaces are there and can be manipulated in the editor. However, they are not styled.

Expected results:

The trailing blanks should be styled. They have almost certainly been styled in the past. Also, they are styled in Chrome. This is a big problem for rich text editors.
Component: Untriaged → Editor
Product: Firefox → Core

Comment 1

6 years ago
Posted image Screenshot
Hmm, I can't reproduce this.  This is what I see.  Am I missing something?

Comment 2

6 years ago
Ehsan: delete the line break and reintroduce it.

Comment 3

6 years ago
Ah, of course, sorry I can't read!  :-)

The issue here is that we incorrectly convert the non-breaking space to a regular space, which gets collapsed and therefore doesn't affect rendering.  This is only one of the thousands of similar types of bugs we have with regards to our incorrect whitespace collapsing behavior in the editor... :(

Comment 4

5 years ago
Still a problem under FF 29.0.1 (Mozilla/5.0 (Windows NT 6.3; WOW64; rv:29.0) Gecko/20100101 Firefox/29.0)
Version: 24 Branch → 29 Branch

Comment 5

2 years ago
This bug is still present in 52.0.1 (Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Firefox/52.0) and is still a problem. 

After loading the testcase, it looks correct. However, after editing (adding spaces at the end) the last space does not get styled. Strangely, the DOM inspector does not show these spaces in the HTML code, but for "Edit as HTML", it is there. Anybody?
You need to log in before you can comment on or make changes to this bug.