428512 - Follow Windows Vista UX "Help" guidelines where possible

Status: RESOLVED INCOMPLETE

(Firefox :: Theme, defect)

Description

[Wesley Johnston (:wesj)]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9pre) Gecko/2008041005 Minefield/3.0pre
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9pre) Gecko/2008041005 Minefield/3.0pre

Well this started as me just seeing the Options dialog in proto and thinking the "Help" icon was neat. Then I noticed that Windows does provide a help-glyph thats included in the "Standard Icons" and that MS encourages applications to use. Then I noticed that the current Help implementation in the prefs panel (a button next to OK/Cancel) is actually listed specifically in the Vista UX guidelines as bad (according to MS, users will ignore it).

So for now the only place I've seen links to help is the prefs pane, where it should probably be a glyph at the top of the panel. Even ignoring the guidelines, three buttons at the bottom of the dialog is getting to be a lot, and moving the help to an icon would make it cleaner.

Reproducible: Always

Comment 1

[Tyler Downer [He/Him]]

This bug was reported using Firefox 3.0 or older, which is no longer supported. The bug has also not been changed in over 500 days and is still in UNCO.
Reporter, please retest this bug in Firefox 3.6.10 or later using a fresh profile, http://support.mozilla.com/en-US/kb/managing+profiles. If you still see this problem, please update the bug. If you no longer see the bug, please set the resolution to RESOLVED, WORKSFORME.

This is a mass search of unconfirmed bugs that have no activity on them, so if you feel a bug was marked in error, just remove the CLOSEME comment in the whiteboard within the next month.

Comment 2

[Tyler Downer [He/Him]]

No reply, INCOMPLETE. Please retest with Firefox 3.6.12 or later and a new profile (http://support.mozilla.com/kb/Managing+profiles). If you continue to see this issue with the newest firefox and a new profile, then please comment on this bug.