129505 - "List Item Properties" defaults to "Change entire list" on Windows

Status: RESOLVED EXPIRED

(SeaMonkey :: Composer, defect)

Description

[michael wendell]

This was found while verifying bug 114832.

Right clicking on a list item and choosing "List Item Properties" defaults to
"Change entire list" instead of Change just selected items.

Steps to reproduce:
1. Launch Composer
2. Click the numbered list icon on the toolbar
3. Create 4 different list items all with different text
4. Right click on the second list item and choose "List Item Properties"

Actual results:
"Change entire list" is selected by default

Expected results:
I would expect that "Change just selected items" would be selected.

Mac OSX using the 03-07 trunk build works as I expected, but Win XP using the
03-07 trunk build does not work as I expected.

Comment 1

[Syd Logan]

Seems like the step "select an item" is missing from the steps.

Even so, selecting an element doesn't help. Assigning to cmanske, mozilla 1.2a

Comment 2

[Charles Manske]

But once you use "Change just selected items", it persists that setting.
I don't think it's terribly bad to default to entire list, since often that is 
what user wants and we shouldn't require them to select each item to do that,
which is impossible if there's a sublist splitting a list:
1. item 1
2. item 2
   1. subitem 1
   2. subitem 2
3. item 3

I'm very inclined to mark "wontfix", but I'll keep open for future discussion.

Comment 3

[Robert Kaiser]

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

Comment 4

[Robert Kaiser]

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