Bug in developer tools
Reported by
bpsnetw...@gmail.com,
Aug 9 2016
|
||||||
Issue description
Chrome Version : 52.0.2743.116
URLs (if applicable) : any
Other browsers tested:
Add OK or FAIL, along with the version, after other browsers where you
have tested this issue:
Safari: OK
Firefox: OK
IE: OK
What steps will reproduce the problem?
(1) Open Developer Tools
(2) Choose the inspector selector
(3) Select an element and watch on any rgba color setting in css
What is the expected result?
I want to see current color of one or another element in color scheme sat up in CSS (HEX,RGBA or RGB)
What happens instead?
It shows any color in HEX, thats the bug, even if you choose RGBA color scheme. So, it can't be normally changed.
Please provide any additional information below. Attach a screenshot if
possible.
,
Aug 10 2016
Tested this on Windows-7, chrome version: 52.0.2743.116 and this worked fine for me there. Attached is the screen-cast of the same. bpsnetwork@: Could you please review the attached screen-cast and confirm if anything being missed here. If possible, please attach the screen-cast of the behavior you are seeing for clearer picture. Thank you!
,
Aug 16 2016
,
Aug 19 2016
bpsnetwork@, could you please respond to comment #2? I'm also unable to reproduce the bad behavior.
,
Aug 19 2016
Thanks for the screencast! From the screencast, it looks like: - you start with a regular 6 digit HEX - DevTools shows it in the styles sidebar - you open the color picker, drag the opacity slider - value changes to 8 digit HEX This is definitely a regression at the moment, since DevTools converts 6 digit HEX to the unsupported 8 digit HEX, when we expect it to go to RGBA. There is a fix that landed in Canary and should reach stable in M53. Sorry for the inconvenience this causes you. Before M53 goes stable, Beta and Canary should be working fine. If you can verify that it works there, I'll close this issue.
,
Aug 22 2016
Confirming that, this is working fine on the latest canary(54.0.2835.0) and the latest beta(53.0.2785.70) on Windows-10 as per the repro steps and the attached screen-cast. bpsnetwork@: Could you please check this on Beta or canary for yourself. You can get the same from here: https://www.chromium.org/getting-involved/dev-channel. Removing the Needs-Bisect label for now as the root cause is identified and Fix is landed as per C#6. Keeping it open for reporter's feedback. Thank you!
,
Aug 25 2016
Issue 640098 has been merged into this issue.
,
Sep 12 2016
Closing since we never heard back. |
||||||
►
Sign in to add a comment |
||||||
Comment 1 by ligim...@chromium.org
, Aug 9 2016