Issue metadata
Sign in to add a comment
|
DevTools: timing function editor incorrectly appears for CSS custom property value
Reported by
razvan.c...@gmail.com,
Jun 8 2016
|
||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/52.0.2743.24 Safari/537.36 Steps to reproduce the problem: 1. Go to http://leaverou.github.io/multirange/ 2. Inspect the element matching: input[type="range"].multirange.ghost 3. Observe the CSS custom property --track-background in the Styles panel What is the expected behavior? What went wrong? The icon to edit a timing function appears next to --track-backgrond value even though the value IS NOT a timing function (it's a linear gradient). The timing function editor appears when clicking the icon. DevTools parsing the value probably gets confused by the word "linear". Did this work before? N/A Chrome version: 52.0.2743.24 Channel: beta OS Version: OS X 10.11.5 Flash Version: Shockwave Flash 22.0 r0
,
Jun 8 2016
Confirmed on 53.0.2756.0
,
Jun 8 2016
,
Jun 8 2016
Not reproduced on 51.
,
Jun 9 2016
Able to reproduce the issue on windows 7, Linux Ubuntu 14.04 and Mac 10.11.5 using chrome version 53.0.2762.0 and beta 52.0.2743.33.It is working fine on stable 51.0.2704.84. This is regression issue broken in M52.Please find the bisect information as below Narrow Bisect ============= Good :: 52.0.2715.0 -- (official build revision 388964) Bad:: 52.0.2716.0 -- (official build revision 389538) CHANGELOG URL: ================ https://chromium.googlesource.com/chromium/src/+log/16c74d1d99fc40179bd660f8cbbcab93ec7b4d8d..8cd882f07ae95e3aca0165feadb5a7c7ca3f6a42 Blink ChangeLog: ================ https://chromium.googlesource.com/external/github.com/catapult-project/catapult.git/+log/380c884ad7fc..966ea3db745c Possible suspect from the above CL https://chromium.googlesource.com/chromium/src/+/010a76f2860a76c36905d58ad0b602da3c037c56 samli@ Could you please look into this issue. Thank you!
,
Jun 9 2016
Moving this nonessential bug to the next milestone. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jul 6 2016
This issue has been moved once and is lower than Pri-1. Removing the milestone. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Nov 3 2016
,
Nov 3 2017
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. If you change it back, also remove the "Hotlist-Recharge-Cold" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Nov 3 2017
,
Dec 20 2017
Can't repro this on Chrome 65. |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by jonathan.garbee@chromium.org
, Jun 8 2016