Open Bug 1004870 Opened 8 years ago Updated 5 years ago

New menu fade effect in Firefox 29 ignores Windows 7 settings

Categories

(Toolkit :: XUL Widgets, defect)

29 Branch
x86_64
Windows 7
defect
Not set
normal

Tracking

()

People

(Reporter: vtqobex, Unassigned)

References

(Blocks 1 open bug)

Details

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:29.0) Gecko/20100101 Firefox/29.0 (Beta/Release)
Build ID: 20140421221237

Steps to reproduce:

In the Windows 7 performance options, uncheck "Fade or slide menus into view". Open the bookmarks menu or options menu in Firefox.


Actual results:

Menus fade into view.


Expected results:

Menus should appear instantly as specified in the Windows settings.
With all due respect, menu effects are time-wasting eye candy and forcing this effect regardless of OS settings was a poor design choice. On a different site someone reported that it's a problem on Macs too, where standard menu behavior is just the opposite of what Firefox does -- menus appear instantly and fade out. Firefox shouldn't force menu behavior across different platforms while ignoring system settings.
Flags: firefox-backlog?
I don't think we have any core APIs to know if this preference is on or not. Dão, Neil, do either of you know?
Flags: needinfo?(enndeakin)
Flags: needinfo?(dao)
We don't have that bug we can add a look and feel option for SPI_GETMENUANIMATION on Windows.
Flags: needinfo?(enndeakin)
Component: Untriaged → XUL Widgets
Flags: needinfo?(dao)
Product: Firefox → Toolkit
Status: UNCONFIRMED → NEW
Ever confirmed: true
Flags: firefox-backlog? → firefox-backlog+
See Also: → 984589
(In reply to Neil Deakin from comment #3)
> We don't have that bug we can add a look and feel option for
> SPI_GETMENUANIMATION on Windows.

How do you think that should integrate with affecting these animations? Should we expose that look and feel option through a CSS pseudoselector, or through XPCOM and then use JS to set an attribute to disable the animations, or did you have something else in mind?

In terms of maintenance and so on, the pseudoselector or the media query would probably be the least annoying to deal with, but it would mean exposing this information to the web, which is something I'm very hesitant about because of privacy and fingerprinting.
Flags: needinfo?(enndeakin)
> How do you think that should integrate with affecting these animations?
> Should we expose that look and feel option through a CSS pseudoselector, or
> through XPCOM and then use JS to set an attribute to disable the animations,
> or did you have something else in mind?

I would pick the former.

> 
> In terms of maintenance and so on, the pseudoselector or the media query
> would probably be the least annoying to deal with, but it would mean
> exposing this information to the web, which is something I'm very hesitant
> about because of privacy and fingerprinting.

I'm not sure why that's a concern.
Flags: needinfo?(enndeakin)
Blocks: 1046570
The problem is worse in Firefox 33, which introduces a new, glitchy menu transition.
See Also: → 1046570
See Also: → 1352069
You need to log in before you can comment on or make changes to this bug.