Issue metadata
Sign in to add a comment
|
Gradient background with bottom border does not fill whole div
Reported by
piotr.sz...@gmail.com,
Jan 10
|
||||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/71.0.3578.98 Safari/537.36 Example URL: Steps to reproduce the problem: Open attachment. What is the expected behavior? Gradient should fill whole div and there should not be white line between border-bottom and div content. What went wrong? White line between border-bottom and div content. NOTE: it is a regression for sure because it worked correctly few weeks ago. Does it occur on multiple sites: Yes Is it a problem with a plugin? No Did this work before? Yes Does this work in other browsers? Yes Chrome version: 71.0.3578.98 Channel: stable OS Version: 6.1 (Windows 7, Windows Server 2008 R2) Flash Version:
,
Jan 11
,
Jan 11
Thanks for filing the issue! Unable to reproduce the issue on reported chrome version 71.0.3578.98 using Windows 10 with the below mentioned steps. 1. launched Chrome 2. Opened "bug.html" in a new tab. In the process we didn't see any white line between border-bottom and div content. Attaching the screenshot of the same for reference. @Reporter: Could you please have a look at the screenshot and let us know if anything is being missed here. Requesting you to share a screenshot of the issue. And please check the same in a new profile without any apps and extensions, let us know if the issue still persist.
,
Jan 11
Thank you for providing more feedback. Adding the requester to the cc list. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jan 11
Additional info: set 125% font size in Windows. If you have 100% font size in Windows then scale Chrome content to 125% to observe same result as in screen.
,
Jan 14
Able to reproduce the issue on reported chrome 71.0.3578.98 and chrome beta 72.0.3626.53 however issue seems to be fixed in latest chrome canary 73.0.3670.0 using Mac 10.14, Windows 10, Windows 7 and Ubuntu 17.10 with steps mentioned in comment #0 and comment #6,hence providing reverse bisect info Note: Able to reproduce the issue on Ubuntu 17.10 using 150% Reverse Bisect Info: ================ Good build: 73.0.3642.0 Bad build: 73.0.3641.0 You are probably looking for a change made after 616943 (known good), but no later than 616944 (first known bad). Change Log: https://chromium.googlesource.com/chromium/src/+log/cefffdd1404635570ba93b9f5f722cddfb93184d..2eed6201bd9ed2c65c7910402d32c036db257fb6 Change-Id: I100575ad4f4fa3004fbc232a72c90b0032ccef4e Reviewed-on: https://chromium-review.googlesource.com/c/1376814 @Stephen Chenney: Please confirm the issue and help in re-assigning if it is not related to your change Adding Release-Block-Stable for M-71, as this is recent regression. Please feel free to remove if not applicable. Thanks..!
,
Jan 14
,
Jan 14
A decision was made not to merge this back. We'll just wait until the changes roll through the release schedule (a few more weeks). |
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by piotr.sz...@gmail.com
, Jan 10