Closed Bug 170436 Opened 22 years ago Closed 14 years ago

Unable to apply advanced property to multiple cells

Categories

(SeaMonkey :: Composer, defect)

defect
Not set
minor

Tracking

(Not tracked)

RESOLVED EXPIRED

People

(Reporter: greg_fenton, Unassigned)

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.1) Gecko/20020826 MultiZilla/v1.1.22
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.1) Gecko/20020826 MultiZilla/v1.1.22

There should be a way to apply a single change to Table Cell Properties to
multiple cells at once.


Reproducible: Always

Steps to Reproduce:
1. In Mozilla, go to http://gonenc.net/mozilla/test1.html
2. File -> Edit Page
3. Select a group of table cells (more than one)
4. Right-click, Table Cell Properties...
5. Advanced Edit...
6. Add the attribute "class", value "mystyle" (defined in that page)
7. Click OK
8. Click Apply

The style is applied to the first cell in the range.  The only way to apply to
other cells is to repeat the above (or from the Properties dialog click the
"Next" button).

Actual Results:  
User loses a LOT of time doing repetitive work.

Expected Results:  
Composer should be a productivity tool; users should not revert to text editors
to accomplish above (and similar) tasks.
--> Composer Table Editing (cmanske)
Assignee: kin → cmanske
Component: Editor: Core → Editor: Composer
This is by design (unfortunately!). Since it may not be clear to the user that
many different settings may be applied to *all* the selected cells, we decided it
was safer to not do that using the results from Advanced Edit changes.
When you are in the regular Cell panel of the Table Propertiess, there are 
checkboxes that let the user control exactly what attributes to apply or not.
E.g., applying the same rowspan or colspan from the current cell to all selected
cells unintentionally would really mess up a table layout!
The only solution I can think of is to popup a message box before appling the 
changes that has these options: "Apply to one cell" "Apply to all selected cells"
and a sentence warning the user about the issue described above.
Does that sound acceptable?
Status: UNCONFIRMED → NEW
Ever confirmed: true
Adding an "apply to all" button is one possible approach, with the above
problems noted.

I have not looked at the code, so take the following with a grain of salt.

Another approach would be to add a new function to "add properties to selected
cells", allowing the user to manually enter a valid cell properties (just like
in the Advanced Edit dialog).  This would only allow for the addition of
properties to the selected cells (and possibly the modification/removal of
existing, COMMON property/value pairs??).
I have this annoyance this on MacOSX as well. 
Tried to change hardware/OS to all/all but I don't have the requisite privileges.
OS: Windows 2000 → All
Hardware: PC → All
Product: Browser → Seamonkey
Assignee: cmanske → nobody
QA Contact: sujay → composer
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 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
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
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: 14 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.