Open Bug 1700865 Opened 2 years ago Updated 1 year ago

maximum amount of pinch zoom depends on app units to dev pixel ratio

Categories

(Core :: Panning and Zooming, defect, P3)

defect

Tracking

()

People

(Reporter: tnikkel, Unassigned)

Details

The app units to dev pixel ratio (from the combination of the user determined full zoom and the value we get from the hardware/os) determines the maximum amount of pinch zoom we are allowed.

Ex if app units to dev pixel ratio is 60 then max pinch zoom is 10x. If app units to dev pixel ratio is 30 then max pinch zoom is 5x. The combination of full zoom and pinch zoom is compared against the max of 10x.

This seems a little weird.

Severity: -- → S3
Priority: -- → P3

Can a regular user currently change this ratio in any reasonable way (i.e. without using a different screen)?

Or, more generally, is it currently possible for a regular user to configure the maximum amount of pinch zoom that is available?

If not, could it be made user-configurable?

(In reply to pbasista from comment #1)

Can a regular user currently change this ratio in any reasonable way (i.e. without using a different screen)?

The browser's reflowing-zoom scale (controlled with Ctrl+Plus/Ctrl-Minus) affects it, but that's presumably not helpful.

Or, more generally, is it currently possible for a regular user to configure the maximum amount of pinch zoom that is available?

If not, could it be made user-configurable?

There is no current way, the values are hard-coded here.

I think making these user-configurable (but still within some wider bounds) is a reasonable request.

Could you file a separate bug for it please? We still want this one to track how the default min/max values are affected by the DPI.

The bug 1753814 requesting that the maximum allowed pinch zoom level is configurable by user has been created.

You need to log in before you can comment on or make changes to this bug.