Closed
Bug 142735
Opened 24 years ago
Closed 16 years ago
Say either "delete row" or "delete rows" etc. in Composer's context menu
Categories
(SeaMonkey :: Composer, enhancement)
Tracking
(Not tracked)
RESOLVED
EXPIRED
People
(Reporter: hakon_, Unassigned)
Details
In the Composer, when you have a table and open the context menu -> Table
Delete... It looks like this:
Row(s)
Column(s)
Cell(s)
But it would be nice if the menu items could adapt to the context, so that e.g.
if it's only one row but two columns selected, it would say:
Row
Columns
Cells
Etcetera... Not an important thing, but it would look neat.
Recommend WONTFIX.
There is already a context menu with context content. The summary of this bug is
somewhat misleading. To adjust all menus for any possible individual combination
of action regarding amount/span sounds like a whole lot of redundant bloat and
would only make menus slower.
Ok. At any case, I change the summary.
Summary: Make the context menu in Composer context sensitive → Say either "delete row" or "delete rows" etc. in Composer's context menu
Comment 4•24 years ago
|
||
Yes, there would be a performance to have to count number of rows in the
selection. Keeping for possible future consideration
Status: UNCONFIRMED → ASSIGNED
Ever confirmed: true
Target Milestone: --- → Future
Updated•21 years ago
|
Product: Browser → Seamonkey
Updated•18 years ago
|
Assignee: cmanske → nobody
Status: ASSIGNED → NEW
QA Contact: sujay → composer
Target Milestone: Future → ---
Comment 5•17 years ago
|
||
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
Comment 6•16 years ago
|
||
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: 16 years ago
Resolution: --- → EXPIRED
You need to log in
before you can comment on or make changes to this bug.
Description
•