121079 - Poor layout of buttons in "Edit Categories" dialog

Status: RESOLVED EXPIRED

(SeaMonkey :: Search, defect)

Description

[David MacKay]

This is not a bug, but a minor design problem.
When one brings up the Search Engines's "Edit Categories" dialog
by clicking in the Sidebar on the "within" menu, 
the dialog box allows the user both to DELETE "categories"
and to ADD and REMOVE "engines" from categories.

IMO, the "Delete" button is poorly placed - it is very close
to the list of "Engines for this category" so a user is
likely to try to "Delete" engines from the category by
hitting the Delete button. After all, it is a shorter distance
away on the screen than the correct "Remove" button!

I suggest making a layout in which a strong dividing element
is placed between the buttons that cause actions like deleting
categories, and the engine-adding-and-removing area.

Comment 1

[Boris Zbarsky [:bzbarsky]]

nothing to do with layout.  Over to search.

Comment 2

[Oliver Klee]

Confirming.

The difference between "Remove" and "Delete" does not seem really clear to me,
BTW. (I haven't tried the buttons yet.)

Comment 3

[Martin Poirier]

"remove" removes a site from the category, while "delete" deletes the whole
category.

Comment 4

[Martin Poirier]

"remove" removes a site from the category, while "delete" deletes the whole
category.

Comment 5

[Samir Gehani]

-> Future

Comment 6

[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 7

[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