Open
Bug 205412
Opened 22 years ago
Updated 3 years ago
backspacing into an empty <ul> halts cursor
Categories
(Core :: DOM: Editor, defect)
Tracking
()
NEW
People
(Reporter: carosendahl, Unassigned)
Details
(Whiteboard: editorbase-)
Attachments
(1 file)
|
271 bytes,
text/html
|
Details |
Test case attached. 20030512 Trunk build
Somehow I managed to get into a state (regardless) where the document contained
empty ul elements.
Backspacing is unable to handle them.
- Open testcase attachment; select "file::edit page"
- Place cursor at the end of the doc and start backspacing.
| Reporter | ||
Comment 1•22 years ago
|
||
Comment 2•22 years ago
|
||
A similar, but different bug is 202046.
Let's revisit this one after we have fixed 202046.
The bug in this testcase is: After you have deleted the second "test" word using
the backspace key, continued backspacing does not delete the other content in
front of the caret.
Depends on: 202046
Comment 3•22 years ago
|
||
It appears this is still broken after having fixed bug 202046.
I'm therefore removing the dependency.
After one has deleted the second word, the cursor jumps up a line, to a position
below the first word.
But still, this position seems to be invalid. Deleting does not work from this
position, possibly because of the invalid position.
When you arrow up, one is not able to go down to the previous position again -
this is why I think it was an invalid position.
Comment 5•22 years ago
|
||
It's not likely that I will work on editor/selection bugs in the near future.
Mass assining my bugs to nobody.
Assignee: kaie → nobody
Comment 7•22 years ago
|
||
snarfing kaie's old bugs
Comment 8•22 years ago
|
||
Bug 215169 related?
Updated•18 years ago
|
QA Contact: bugzilla → editor
Updated•18 years ago
|
Assignee: mozeditor → nobody
Updated•3 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•