New issue
Advanced search Search tips

Issue 708509 link

Starred by 3 users

Issue metadata

Status: WontFix
Owner: ----
Closed: Apr 2017
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 2
Type: Bug



Sign in to add a comment

Incorrect work of zoom/scale switch of device toolbar in responsive design mode.

Reported by ser.meli...@gmail.com, Apr 5 2017

Issue description

UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.87 Safari/537.36

Steps to reproduce the problem:
Enter Web Inspector, toggle device toolbar and try to change zoom factor in responsive design mode.

https://youtu.be/GatNeH901jc

What is the expected behavior?
If you’re working with presets — everything works ok, you can correctly zoom in/zoom out to see rendered output in specific scale (if you need to develop for device with custom dpi for example). 

What went wrong?
If you enter responsive design mode — view is always set Fit in window and zoom changes layout but not zoom of rendered layout

Did this work before? N/A 

Chrome version: 56.0.2924.87  Channel: n/a
OS Version: OS X 10.12.4
Flash Version: 

For example. I have 27 inch QHD monitor and want to test how my webapp layout will work on 33 inch 5k monitor (it can be rotated, splitted natively, etc. hundreds of presets i do not want to keep) so i enter the responsive design mode and enter 5120 × 2880 resolution, or 2880 × 5120, or 2560 × 2880, etc. but if I want to check visually for issues and see if it okay in pixel-to-pixel, so I set 100% scale… but it changes the resolution to 1557 × 687 (size of my current real viewport) causing different layout!
 
Status: WontFix (was: Unconfirmed)
This is caused because the resolution that is being used is larger than can be shown on the screen, so we are forced to zoom the page to show the entire page inside the viewport. It is possible to use a combination of "Ctrl +" (chrome's zoom) and custom Device-Pixel-Ratio (in Edit menu) and zoom to achieve what I believe you are looking for.

This is a tricky area because no matter what we do it will not satisfy everybody and over the last few years we have to deal with cases where "px" no longer means "pixel" and trying to keep simplicity (for the majority) and the ability for complex visual debugging (like for for DIP) is difficult.

Thanks for the bug report though!

Sign in to add a comment