A wired dev tool bug - Quantitive and qualitative values stuck when changed
Reported by
ben...@gmail.com,
Aug 31 2016
|
|||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:48.0) Gecko/20100101 Firefox/48.0 Steps to reproduce the problem: 1. Change quantitative or qualitative values in Chrome. What is the expected behavior? What went wrong? I encounter what seems to be a bug in Chrome dev tools. It happens after "Restore default and reload"/update/reinstall. The bug: When I change padding/margin for some <div> tags (or any other element), after the first pixel changes, it stucks. For example: If I reduced from 20 pixels, it will stuck in 19 pixels, and change won't be seen in 18 or downwards... Note: Similar problems occur with qualitative values as well; For example: Changing to a second color after the first color change wouldn't happen in the dev tool in Chrome. Any of these problems do not occur in Firefox or Edge. It happens only in Chrome. It happens for some months now. My Chrome Version is 52.0.2743.116 m (64-bit). Did this work before? N/A Chrome version: <Copy from: 'about:version'> Channel: stable OS Version: 10.0 Flash Version: VLC media player Web Plugin I use Windows 10 Home preview insider build, though if it was associated, the problem would most likely to occur in Edge and Firefox.
,
Sep 1 2016
,
Sep 2 2016
Milestone, I've now noticed it happens only for the Web (CentOS Production) version of my site. But when I check a local WAMP version of my site, it doesn't happen. This seems to be caused due to a problematic connection between Chrome and my server. If a link to my site is needed, I will attach it.
,
Sep 6 2016
Milestone: It happens only when the Drupal 8 caching is on; Seems also when the module AdvAgg is on.
,
Sep 8 2016
Seems not to be associated to AdvAgg but to the Drupal cache only, under admin/config/development/performance
,
Dec 5 2017
Sorry for the long reply. I failed to reproduce this on Chrome 65.0.3285.0 and google.com website. If you have a good link that illustrates the issue for you (and it still exists), we'll be happy to look into it. Speculatively closing this for now since it might've been fixed. |
|||
►
Sign in to add a comment |
|||
Comment 1 by rnimmagadda@chromium.org
, Sep 1 2016