Closed Bug 167851 Opened 22 years ago Closed 15 years ago

Can't delete column from triangular table

Categories

(SeaMonkey :: Composer, defect)

x86
Windows 2000
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED EXPIRED

People

(Reporter: timeless, Unassigned)

Details

(Keywords: polish)

Attachments

(1 file)

@see bug 166922 20002091008w32talkback(.zip) +===v---\ H 1 L | >====___J H 3 H 4 H +===^===+ place cursor at 4 right click delete table>column(s) expect: column to be deleted. actual results: nothing happened.
Attached file testcase
-->cmanske
Assignee: syd → cmanske
I'm not surprised! It's not a very nice table.
Status: NEW → ASSIGNED
Target Milestone: --- → mozilla1.2beta
Keywords: nsbeta1, polish
Composer triage team: nsbeta1-
Keywords: nsbeta1nsbeta1-
I suggest resolving as WONTFIX or INVALID since table cell 4 only could have been created, inserted while in <HTML> source editing mode and not in Normal nor HTML Tags editing mode. So, it seems logical to expect the user to correct his edition decision/error by making changes in that same editing mode.
Product: Browser → Seamonkey
Assignee: cmanske → nobody
Status: ASSIGNED → NEW
QA Contact: sujay → composer
Target Milestone: mozilla1.2beta → ---
MASS-CHANGE: This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state. If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way. If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar). If no action happens within the next few months, we move this bug report to an EXPIRED state. Query tag for this change: mass-UNCONFIRM-20090614
Status: NEW → UNCONFIRMED
MASS-CHANGE: This bug report is registered in the SeaMonkey product, but still has no comment since the inception of the SeaMonkey project 5 years ago. Because of this, we're resolving the bug as EXPIRED. If you still can reproduce the bug on SeaMonkey 2 or otherwise think it's still valid, please REOPEN it and if it is a platform or toolkit issue, move it to the according component. Query tag for this change: EXPIRED-20100420
Status: UNCONFIRMED → RESOLVED
Closed: 15 years ago
Resolution: --- → EXPIRED
This bug needs to be reopened. It's still there, not just in the trunk, but in all releases. So RESOLVED is not the right status and neither is EXPIRED. One might argue changing the status to WONTFIX, but Gérard Talbot's comment #5 is invalid: it's perfectly possible to create a table like that without ever going to source mode (select two adjacent cells and "Join selected cells", then edit the cell properties and remove the colspan attribute). Unfortunately, I don't seem to have the permissions to request a change in status.
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: