Open
Bug 1921180
Opened 1 month ago
Updated 17 hours ago
Use `U+000A`(`LF`) instead of `<br>` when `contenteditable=plaintext-only` and the line breakers are preformatted by `white-space`
Categories
(Core :: DOM: Editor, defect)
Core
DOM: Editor
Tracking
()
NEW
People
(Reporter: masayuki, Unassigned)
References
(Depends on 2 open bugs, Blocks 4 open bugs)
Details
(Keywords: parity-chrome, parity-safari)
Chrome loves linefeed characters instead of <br>
in contenteditable
. Changing the behavior for contenteditable=true
might be risky. I think that we should change our behavior only for contenteditable=plaintext-only
first.
However, probably we need to change the behavior of inserting padding <br>
for empty editor and last line since web apps do not assume linefeed and <br>
s are mixed in same editing host.
Reporter | ||
Comment 1•24 days ago
|
||
Ah, textContent
does not convert <br>
to \n
. So, it might be important to support this.
It seems that it's okay to use <br>
for empty paragraph. It's same as Chrome and Safari. However, they delete the padding <br>
at typing something. We should follow it.
Keywords: parity-chrome,
parity-safari
You need to log in
before you can comment on or make changes to this bug.
Description
•