box-shadow not correctly rendered when using small spread values
Reported by
backesch...@gmail.com,
Aug 1 2017
|
|||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/60.0.3112.78 Safari/537.36 Steps to reproduce the problem: See below What is the expected behavior? What went wrong? box-shadow is not correctly rendered when using small spread values. Please visit https://goo.gl/wLWgDp for live testing and click on the "Absenden" button. You have to use 4K or WQHD, I don't know if the bug also occurs on Full HD. Login data: Username: google Password: dev Did this work before? N/A Does this work in other browsers? No Firefox have similar problems: https://bugzilla.mozilla.org/show_bug.cgi?id=1386150 Chrome version: 60.0.3112.78 Channel: stable OS Version: 10.0 Flash Version: Shockwave Flash 26.0 r0
,
Aug 1 2017
4K is highly recommendable for development :) You can try it also with 2px or 3px spread on 'box-shadow'. One will see then right and bottom of the textarea incorrectly rendered. What do you mean by 'manifest'? For me it is clearly visible something is wrong with the painting.
,
Aug 1 2017
In this case "manifest" means "appear". Sorry for the confusion. Thanks for the info on 2px and 3px. In the images you posted it seems the border thickness varies around the box. Is that what you are reporting?
,
Aug 1 2017
In the screenshots the border is removed to show the effect better: border: 0; box-shadow: 0 0 0 2px #F76B68; So the "border" is the box-shadow which thickness is inconsistent, correct :)
,
Aug 1 2017
5px shows the same. What effectively is missing is the "shadow pixel". What I mean is the slightly brighter pixel to make the shadow effect (so on 2px spread it is 2px with the choosed color and 1px of a brighter color). For me it seems to be a scaling problem. It depends on zoom/'font-size' (which is increased on higher resolutions).
,
Aug 2
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. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Aug 2
|
|||
►
Sign in to add a comment |
|||
Comment 1 by schenney@chromium.org
, Aug 1 2017Status: Available (was: Unconfirmed)