Closed
Bug 16481
Opened 25 years ago
Closed
[DOGFOOD]Deleting text in table deletes table cells
Categories
(Core :: DOM: Editor, defect, P1)
Tracking
()
VERIFIED
FIXED
M12
People
(Reporter: cmanske, Assigned: mozeditor)
References
Details
(Whiteboard: [PDT+][by 12/3])
When using the delete key or backspace to delete contents in a table cell, after the last text character or element is deleted, the table cell is deleted. It should not. It should skip over to the contents of the previous cell when using backspace, or just stop deleting when using the delete key. Otherwise holding down delete or backspace really messes up your table structure!
Assignee | ||
Comment 1•25 years ago
|
||
accepting/m11
Updated•25 years ago
|
Severity: normal → major
Priority: P3 → P1
Summary: Deleting text in table deletes table cells → [DOGFOOD]Deleting text in table deletes table cells
Comment 2•25 years ago
|
||
submitting this as a dogfood candidate -- deleting the actual cell is not a good thing, it will actually affect the entire layout of the page in many instances.
Updated•25 years ago
|
Target Milestone: M11 → M12
Comment 4•25 years ago
|
||
this will need a deletion rules for table elements, this is going to take some time to do. Joe knows what to do but it will not be done by today. Moving over to M12
If there is a workaround, let's make this PDT- and put workaround into: http://bugzilla.mozilla.org/show_bug.cgi?id=17788 Otherwise, yes fix for dogfood.
Updated•25 years ago
|
Whiteboard: [PDT+] → [PDT+][by 11/19]
Comment 7•25 years ago
|
||
this one has been investigated, joe has a good idea on how to fix it
Assignee | ||
Updated•25 years ago
|
Target Milestone: M12 → M13
Assignee | ||
Comment 8•25 years ago
|
||
In progress. revising estimate to 12/3
Updated•25 years ago
|
Whiteboard: [PDT+][by 11/19] → [PDT+][by 12/3]
Target Milestone: M13 → M12
Assignee | ||
Comment 9•25 years ago
|
||
I'm finally starting this. Still estimate a 12/3 resolution.
Assignee | ||
Comment 10•25 years ago
|
||
fixed. should make this mornings verification builds. The behvior now is: If you have an insertion point and hit delete or forward delete, you will stop when you get to the boundary of any table element. If you have a selection range highlighted and hit delete or forward delete, nothing will happen if your selection endpoints reside in different table elements (including one in a table element and one not). Note that the various insert operations will implicitly delete a selection range. These actions do not yet play by these deletion rules. That's a sperate bug. I need to make sure that everything that implicitly deletes, does so via the rules code so that we get a chance to cancel illegal table deletions.
Comment 11•25 years ago
|
||
verified in 12/1 build.
You need to log in
before you can comment on or make changes to this bug.
Description
•