Consider moving element metrics inspector into a drawer (feature request)
Reported by
iwasawa...@gmail.com,
Apr 30 2017
|
||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/58.0.3029.81 Safari/537.36 Steps to reproduce the problem: 1. Open dev tools with vertical layout, try to inspect element. 2. Go to the Styles pane, scroll past all the style blocks and locate metrics inspector 2. Switch devtools to horisontal layout, notice how computed tab is always visible on the right along with metrics inspector and it doesn't go away from the screen when Styles is being scrolled What is the expected behavior? I would love having metrics inspector always visible on vertical layout. What went wrong? Right now it's not possible to edit a value in the upper style block and monitor changes on the metrics inspector without scrolling back and forth when dev tools displayed with vertical panel layout Did this work before? No Chrome version: 58.0.3029.81 Channel: stable OS Version: 6.1 (Windows 7, Windows Server 2008 R2) Flash Version: Seeing calculated numbers change as soon as you adjust some of the CSS properties could make life much easier especially when hunting down particular value in pixels from mockups while dealing with relative units like em or percents. I guess some may say that using math for finding correct value is a way to go, but not thinking is easier than thinking, especially when one is tired. And so I'd really prefer having those metrics pinned to the bottom of the pane or maybe sitting in some kind of collapsible drawer, similarly to state modifiers. When dev tools is open in a standalone window and there's enough vertical space it doesn't hurt to have it visible all the time (see the attached image for example)
,
May 2 2017
This looks more like a feature request and hence marking it as untraiged , for further inputs on this. Thanks!
,
May 2 2017
,
Dec 11 2017
WontFix due to lack of priority / resources |
||||
►
Sign in to add a comment |
||||
Comment 1 by eostroukhov@chromium.org
, May 1 2017