Open
Bug 270438
Opened 20 years ago
Updated 4 years ago
Table delete-column widget doesn't work for unusual cell array
Categories
(Core :: DOM: Editor, defect, P5)
Tracking
()
NEW
People
(Reporter: mcow, Unassigned)
Details
Due to various tweaks using things like 'rowspan' you can get a table into a somewhat odd configuration where a cell has no neighbor in its column or row. When this happens, and the cell is selected, the row/column widgets don't work particularly well. To reproduce: 1) In Composer, insert a 2x2 table. 2) Select the upper-left cell; using Properties, Advanced Edit, add an attribute: rowspan = 2. The table now looks like this: +-----+-----+ + + + + +-----+-----+ + + + + +-----+-----+-----+ 3) Select the bottom-right-most cell, the one that's sticking out. The column widgets are shown on its top and left borders. 4) Click the (x) widget (delete row) on the top border. Actual results: No change Expected results: Cell is deleted. There are other goofy things that can happen with these odd configurations, but this one is particularly annoying because it would be a simple way to "fix" the table after changing the 'rowspan' attribute. The workaround is to need to delete the cell via the menu. However, in the mail composer, that option is buried under Format|Table|Delete|Cell(s) rather than being on the context menu. I see this in Moz 1.8a5 Composer and MailNews, NVu 0.4, TB 0.9.
Updated•20 years ago
|
Product: Browser → Seamonkey
Comment 1•16 years ago
|
||
Can you reproduce with SeaMonkey v1.1.9 ? (or Thunderbird v2.0.0.14 ?)
Assignee: composer → nobody
Component: Composer → Editor
Product: Mozilla Application Suite → Core
QA Contact: editor
Version: Trunk → 1.8 Branch
| Reporter | ||
Comment 2•16 years ago
|
||
I can reproduce it with TB 3a1pre-0419.
Comment 3•4 years ago
|
||
Bulk-downgrade of unassigned, >=5 years untouched DOM/Storage bugs' priority and severity.
If you have reason to believe this is wrong, please write a comment and ni :jstutte.
Severity: minor → S4
Priority: -- → P5
You need to log in
before you can comment on or make changes to this bug.
Description
•