Closed Bug 589121 Opened 15 years ago Closed 15 years ago

Hovering over menuitem shows black on blue instead of white on blue on WinXP and Win7/Classic

Categories

(Firefox :: Theme, defect)

x86
Windows 7
defect
Not set
normal

Tracking

()

RESOLVED FIXED
Firefox 4.0b7
Tracking Status
blocking2.0 --- final+

People

(Reporter: alice0775, Assigned: dao)

References

Details

(Keywords: regression)

Attachments

(3 files, 3 obsolete files)

Attached image screenshot
Build Identifier: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:2.0b5pre) Gecko/20100820 Minefield/4.0b5pre ID:20100820020849 http://hg.mozilla.org/mozilla-central/rev/1504917ed42e In Windows Classic Style, Hovering menuitem shows black on blue instead of white on blue. Text color should be white. This problem looks like Bug 571871.
Component: Menus → Theme
QA Contact: menus → theme
Target Milestone: Firefox 4.0 → ---
Are we supporting the menubutton on Windows Classic?
(In reply to comment #1) > Are we supporting the menubutton on Windows Classic? I think we should. At least the draw-in-titebar stuff should already work in the classic theme (when the patch is checked in again). And disabling the button when the user switches the theme seems more difficult than just supporting it.
(In reply to comment #1) > Are we supporting the menubutton on Windows Classic? Yes. This bug affects more than classic, though.
Summary: [Firefox Menu Button]Hovering menuitem shows black on blue instead of white on blue in Windows Classic Style → Hovering over menuitem shows black on blue instead of white on blue on WinXP and Win7/Classic
The patch in bug 589163 fixes this for some items.
Depends on: 589163
(In reply to comment #1) (From https://bugzilla.mozilla.org/show_bug.cgi?id=580738#c3) > The "menu button" jumplist? doesn't exist on "Windows Classic" > theme (see https://bugzilla.mozilla.org/attachment.cgi?id=467794). > I'm not UI expert, but I believe for classic theme only the elements on > Classic.xaml should be used (see > http://msdn.microsoft.com/en-us/library/aa970773.aspx)
Attached image another ss
blocking2.0: --- → ?
blocking2.0: ? → final+
With the beta 5 (build 1] it is ok with Win7 Basic/Aero Design. Mozilla/5.0 (Windows NT 6.1; WOW64; rv:2.0b5) Gecko/20100101 Firefox/4.0b5 (the build date is wrong, should be 20100831)
Assignee: nobody → dao
Attached patch Patch v1 (obsolete) — Splinter Review
I think it works properly.
Attachment #472463 - Flags: review?(dao)
Attached patch Patch v1 + little fix (obsolete) — Splinter Review
Little fix about edit menuitem.
Attachment #472463 - Attachment is obsolete: true
Attachment #472476 - Flags: review?(dao)
Attachment #472463 - Flags: review?(dao)
Comment on attachment 472476 [details] [diff] [review] Patch v1 + little fix This looks like it will slow down interaction with every menu or menuitem in the window... not cool.
Attachment #472476 - Flags: review?(dao) → review-
Attached patch Patch v2 (obsolete) — Splinter Review
Dao now CSS rules seems to be better. I hope now it's cool ;)
Attachment #472476 - Attachment is obsolete: true
Attachment #472566 - Flags: review?(dao)
Comment on attachment 472566 [details] [diff] [review] Patch v2 > <menupopup id="appmenu-popup" > onpopupshowing="updateEditUIVisibility();"> > <hbox> >- <vbox id="appmenuPrimaryPane"> >+ <vbox id="appmenuPrimaryPane" class="split-menuitem"> > <hbox flex="1" > class="split-menuitem"> > <menuitem id="appmenu_newTab" >- class="split-menuitem-item" > flex="1" > label="&tabCmd.label;" > command="cmd_newNavigatorTab"/> appmenuPrimaryPane isn't a split menuitem. Setting the split-menuitem class there is not cool ;-) Thanks for looking into this, but I already have a pretty simple patch, just need to test it.
Attachment #472566 - Flags: review?(dao) → review-
Ok, thanks Dao! :)
Attached patch patchSplinter Review
Attachment #472566 - Attachment is obsolete: true
Attachment #472574 - Flags: review?(gavin.sharp)
Comment on attachment 472574 [details] [diff] [review] patch Why is the -moz-padding-end removal OK? Why do we need to specify these styles at all anyways? Can the answer to that be in a comment?
(In reply to comment #16) > Comment on attachment 472574 [details] [diff] [review] > patch > > Why is the -moz-padding-end removal OK? It was there to align the keyboard shortcuts. They're gone, so it's not needed anymore, and the selector doesn't actually match anything anymore. > Why do we need to specify these styles at all anyways? Can the answer to that > be in a comment? See bug 571871 comment 6. I can add a comment.
Comment on attachment 472574 [details] [diff] [review] patch please do add the comment
Attachment #472574 - Flags: review?(gavin.sharp) → review+
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 4.0b6
I now see white on blue on WinXP Classic using Mozilla/5.0 (Windows NT 6.0; rv:2.0b6pre) Gecko/20100910 Firefox/4.0b6pre ID:20100910041829 Thanks Mr. Gottwald!
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: