Contenteditable=false elements in contenteditable=true elements cannot be deleted by using Backspace
Categories
(Core :: DOM: Editor, defect)
Tracking
()
People
(Reporter: ioana_damy, Unassigned, NeedInfo)
References
Details
Attachments
(1 file)
|
945 bytes,
text/html
|
Details |
Comment 1•15 years ago
|
||
| Reporter | ||
Comment 3•15 years ago
|
||
Comment 6•12 years ago
|
||
Comment 7•12 years ago
|
||
Comment 10•12 years ago
|
||
Comment 11•11 years ago
|
||
Comment 12•11 years ago
|
||
Comment 13•11 years ago
|
||
Comment 14•11 years ago
|
||
Comment 15•10 years ago
|
||
Updated•9 years ago
|
Comment 17•8 years ago
|
||
Comment 18•7 years ago
|
||
Comment 19•7 years ago
|
||
v66.0 - still reproducible. This is marked as a duplicate and resolved.
I cannot find an open bug related to this issue. Can we re-open this (as the earliest reference to this bug) so that the issue is tracked?
Comment 20•6 years ago
|
||
We are still seeing this issue in FF 72.0.1 (Mac); example: https://jsfiddle.net/063bmd4u/1/.
Comment 21•6 years ago
|
||
(In reply to jeff from comment #20)
We are still seeing this issue in FF 72.0.1 (Mac); example: https://jsfiddle.net/063bmd4u/1/.
I am having the same annoyances which greatly affects a plugin of mine which is used by thousands (https://www.npmjs.com/package/@yaireo/tagify)
As Jeff showed, this is still happens, and also there are caret issues (it isn't shown)
Comment 22•6 years ago
|
||
Bug still exists in Firefox mac 78.0.1 (a colleague said she sees in on windows)
Even if you inspect a content editable field, edit its html and then add <span contenteditable="false">hello?</span> it wont be deleteable.
Note: we have notice that contenteditable="false" elements added while focussed are able to be deleted, but if you blur and refocus or they pre exist before focus the are not able to be deleted.
Comment 23•6 years ago
|
||
Update... I also noticed that if i add a <span contenteditable="true"></span> after the contenteditable="false" el i cant delete that the act of deleting the contenteditable="true" one seemed to make it possible to delete the contenteditable="false" one.
So thats how I will be "fixing" this issue currently, which is awful :(
Comment 24•6 years ago
|
||
This bug has been reported as early as ~10 years ago and had been marked multiple times as "resolved". However, in mid September year 2020, it is not resolved and is in fact still an active bug.
As others have stated, when building a custom input using "contenteditable=true", if you inject an inline html element e.g. a <span> with <span contenteditable="false">, only in mozilla firefox can you not delete this element. When the caret reaches the right side of the inline <span>, it will both vanish (you can no longer see it), and you cannot delete the inline element. In all other browsers the element will be deleted with no noticeable glitches.
Is Mozilla working on this bug? Given that "contenteditable" is an increasingly common feature, and many popular javascript frameworks use it, I am surprised this bug still exists.
A simple google "firefox contenteditable backspace" will reveal numerous postings about this issue across many javascript projects, bug reports, and stackoverflows.
Please update us, thank you.
Comment 25•6 years ago
|
||
Commenting on closed bugs is unlikely to get much attention. If something regresses, it's better to file a new bug. I opened bug 1665167 for that, as I can trivially reproduce.
Comment 26•6 years ago
|
||
ok great thank you Emilio!
Description
•