Uploaded image for project: 'JDK'
  1. JDK
  2. JDK-6379098

REGRESSION: Disabled icons in Windows L&F don't look disabled in Mustang

XMLWordPrintable

    • b84
    • generic, x86
    • generic, windows_xp

      FULL PRODUCT VERSION :
      java version "1.6.0-rc"
      Java(TM) 2 Runtime Environment, Standard Edition (build 1.6.0-rc-b69)
      Java HotSpot(TM) Client VM (build 1.6.0-rc-b69, mixed mode, sharing)

      ADDITIONAL OS VERSION INFORMATION :
      Microsoft Windows XP [Version 5.1.2600]

      A DESCRIPTION OF THE PROBLEM :
      In the Windows Look-and-Feel under JDK 1.6, the disabled icons don't look
      disabled. Although they're distinct from the enabled ones, they're not
      gray enough to look disabled, and their contrast is still very sharp. Users
      get confused when they see them.

      STEPS TO FOLLOW TO REPRODUCE THE PROBLEM :
      Run the test program under Windows XP. Toggle the icons to their disabled
        state, then ask some unbiased observer to tell you which ones are enabled.
      (Don't let them see the icons in the enabled state.) Chances are they'll
      tell you the first two are enabled, or they're not sure. If they're not
      sure, the icons aren't grayed-out enough. There's too much contrast in their
      disabled state for them to look disabled.


      EXPECTED VERSUS ACTUAL BEHAVIOR :
      EXPECTED -
      Icons should look clearly disabled when they are disabled.
      The contrast should be poor, and they should pass the "unbiased obsever"
      test with flying colors. The results should be consistent with Microsoft
      Windows icons, but the actual disabled Microsoft icons have very low
      contrast, noticably lower than these icons.

      ACTUAL -
      Unbiased observers tend to be unsure about whether or not they're disabled


      REPRODUCIBILITY :
      This bug can be reproduced always.

      ---------- BEGIN SOURCE ----------
      Attached seperatly
      ---------- END SOURCE ----------

      Release Regression From : 5.0u6
      The above release value was the last known release where this
      bug was known to work. Since then there has been a regression.

            rbair Richard Bair (Inactive)
            ndcosta Nelson Dcosta (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved:
              Imported:
              Indexed: