Open
Bug 1138704
Opened 11 years ago
Updated 1 year ago
Mouse-wheel zoom does not honour the toolkit.zoomManager.zoomValues preference
Categories
(Core :: DOM: Events, defect, P5)
Core
DOM: Events
Tracking
()
NEW
People
(Reporter: ldubox-coding101, Unassigned)
References
Details
User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:37.0) Gecko/20100101 Firefox/37.0
Build ID: 20150223185154
Steps to reproduce:
1. Using about:config, set
toolkit.zoomManager.zoomValues = .3,.5,.67,.8,.86956,1,1.1,1.2,1.33,1.5,1.7,2,2.4,3
2. Zoom out one 'click' using Ctrl+mouseWheel
Actual results:
Zoom level in the main menu shows as 90%
Expected results:
Zoom level in the main menu shows as 87%. This is the result if you use the main-menu zoom controls, or the keypress Ctrl+ -
| Reporter | ||
Comment 1•11 years ago
|
||
More info: this setting was particularly useful for me after upgrading to a new 2560x1440 monitor, as I needed to set Windows DPI scaling to 115% to read fonts comfortably. (Which I'm discovering Firefox handles very gracefully - nice work!)
Introducing the zoom level of .86956 'cancels' the DPI scaling, e.g. so that I can see bitmap images nice and crisply without scaling, which is often useful.
Updated•11 years ago
|
Component: Untriaged → Panning and Zooming
Product: Firefox → Core
Comment 2•11 years ago
|
||
I think this code lives in EventStateManager::ChangeFullZoom.
Component: Panning and Zooming → DOM: Events
I confirm this bug reproduces but it's not a bug introduced in Firefox 37. It reproduces back at least as far as Firefox 29. It probably goes back further but I'm not sure how to test this in pre-Australis builds.
Status: UNCONFIRMED → NEW
Ever confirmed: true
OS: Windows 7 → All
Hardware: x86_64 → All
Version: 37 Branch → Trunk
Updated•7 years ago
|
Priority: -- → P5
Updated•3 years ago
|
Severity: normal → S3
Comment 4•3 years ago
|
||
Bump.
Comment 6•1 year ago
|
||
I just noticed this weird behavior and wanted to file a bug.
Hope that this bug reported 10 years ago will be fixed soon, it's quite annoying. 😞
You need to log in
before you can comment on or make changes to this bug.
Description
•