67769 - Layout/logic problems with `Use system colors' checkbox

Status: RESOLVED EXPIRED

(SeaMonkey :: Preferences, defect, P3)

Description

[Matthew T (active 1999-2002)]

Build: 2001020513, Mac OS 9.0

To reproduce:
*   Open the `Colors' panel in Preferences.
*   Check the `Use system colors' checkbox.

What you see:

    +-Text and Background------+ +-Link Colors--------------+
    |                          | |                          |
    | Text:               [##] | | Unvisited Links:    [@@] |
    | Background:         [  ] | | Visited Links:      [QQ] |
    | [/] Use system colors    | | [/] Underline links      |
    +--------------------------+ +--------------------------+

What you should see on Windows:

    [/] Use system settings

        :  : Backgrounds    [@@] Links
        :##: Text           [OO] Recent links

        [/] Underline links

What you should see on Mac OS:

    [/] Use system settings

        :  : Backgrounds    :@@: Links
        :##: Text           :OO: Recent links

        :/: Underline links

In other words, the following needs to happen.
*   The `Use system colors' checkbox should be renamed `Use system settings'.
*   Checking the checkbox should disable controls which no longer have any
    effect:
    -   on Windows, the `Text' and `Background' controls
    -   on Mac OS, the `Text', `Background', `Links', `Recent links', and
        `Underline links' controls.
*   Checking the checkbox should set all these disabled controls to accurately
    reflect the system settings, so that the user can quickly see what the system
    settings are. (Otherwise, how do you know if you really want to use them?)
    Unchecking the checkbox should return the controls to the custom settings
    which the user last had selected before the checkbox was checked.
*   The `Use system settings' checkbox should be moved above the other controls,
    and the other controls should be indented under it, to indicate that the
    state of the checkbox determines whether the other controls have any effect.

Comment 1

[Keyser Sose]

*** Bug 69953 has been marked as a duplicate of this bug. ***

Comment 2

[Samir Gehani]

Taking.

Comment 3

[Samir Gehani]

Moving to mozilla0.9.8.

Comment 4

[Samir Gehani]

Moving to milestone after mozilla0.9.9 (mozilla1.0 for now).

Comment 5

[Peter Trudelle]

Samir has a patch in bug 79603 to disable the unused controls.  The rest are
minor issues that we can consider changing the spec for in a future release. 
->future

Comment 6

[Peter Trudelle]

Mass move of nsbeta1+ bugs that didn't have a valid MachV milestone to mozilla1.0.

Comment 7

[Samir Gehani]

The nsbeta1+ was legacy cruft from way back when I was triaging and the only way
I was allowed to leave things in mozilla1.0 was by nsbeta1+'ing the bug.  Moving
back to Future.

Comment 8

[Alessandro Minelli]

Wontfix?

Comment 9

[Robert Kaiser]

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 10

[Robert Kaiser]

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 11

[Robert Kaiser]

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 12

[Robert Kaiser]

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 13

[Robert Kaiser]

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 14

[Robert Kaiser]

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 15

[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