Issue metadata
Sign in to add a comment
|
multiple borders with rgba colors aren't working/showing anymore
Reported by
nils.ber...@gmail.com,
Jun 7 2017
|
||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/59.0.3071.86 Safari/537.36 Steps to reproduce the problem: 1. create a div with border-top:1px solid rgba(173, 237, 255, 0.15); and border-bottom:1px solid rgba(173, 237, 255, 0.15); What is the expected behavior? usually a top and bottom border with the given color shows up. What went wrong? the borders have shown up in #58 but not in #59, if you remove one of the border elements it works if you change the colors to hex it also works, but not with two rgba borders. Did this work before? Yes 58 Chrome version: 59.0.3071.86 Channel: stable OS Version: OS X 10.12.5 Flash Version:
,
Jun 8 2017
,
Jun 8 2017
same on my side, only difference i'm on [windows 10], that occured just after updating chrome to v59. 3 tips: -that happend also for left/right -seems happend only when the 2 values of the 2 properties is equal and use rgba ex:(top:1px...; / bottom:2px...;) it work! ex:(top:...rgba(0,0,0,0.11); / bottom:...rgba(0,0,0,0.12);) it work! ex:(top:... red; /bottom:... red;) it work! ex:(top:... rgb(0,0,1); /bottom:... rgb(0,0,1);) it work!
,
Jun 9 2017
[Mac triage] Over to Blink, though FWIW, this doesn't repro for me in either stable or Canary with the given JSFiddle
,
Jun 9 2017
I have tryed it on my personnal computer which is also a windows 10 computer, and add a screenshot of the jsfiddle. -i did it in private mode to exclude any extension -i also reset all my "chrome://flag" to default I'll try to find a v58 to try to take a new picture.
,
Jun 9 2017
here you ll find a picture with v58 in the same condition.
,
Jun 11 2017
On my internal screen on my MacBook it works fine with the borders but as soon as I plug in my external monitor it doesn't work anymore and shows up broken/not visible.
,
Jun 11 2017
hum? reading your comment i've just take a look on my GPU driver. That was not up to date... i have a 980 GTX ti, and i updated driver to v382.53 and after that everything appear fine, has you can see on the picture. I dont really understand why because i thought only few css properties using GPU. I'll test it tomorrow on my computer at work.
,
Jun 12 2017
Tested the issue on Mac os 10.12.5 using chrome M59 #59.0.3071.86 and M58 #58.0.3029.110 and observed different behavior as attached in screenshots. @nils.berenbold-- Could you please check attached screenshot and confirm if M58 behavior is the expected behavior , so that we can continue bisecting the issue. Thanks!
,
Jun 14 2017
Here's a test case for the bug. Can reproduce with minimal css. https://jsfiddle.net/xz9euh4y/ This is currently breaking pretty much all production sites I've worked on since rgba spec was implemented. As an outsider I would call this high priority.
,
Jun 14 2017
@hdodda@chromium.org Yep the 58 is how it should look, correct.
,
Jun 14 2017
Thank you for providing more feedback. Adding requester "hdodda@chromium.org" to the cc list and removing "Needs-Feedback" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jun 15 2017
Tested the issue on mac os 10.12.5 using chrome M59 #59.0.3071.86 and issue is reproduced. This is a regression issue broken in M60 and is fixed in latest beta dev and canary channels. It is reproduced only on Mac OS. Using the old bisect script providing the reverse bisect results, Good build: 60.0.3096.0(Revision: 470759). Bad build: 60.0.3094.0 (Revision: 470111). You are probably looking for a change made after 470313 (known good), but no later than 470324 (first known bad). CHANGELOG URL: https://chromium.googlesource.com/chromium/src/+log/1073d1c2e24a31bc6c34bbc6a6c198ae5d668086..175ceeff6a099a7923928ba8fcd58c6b80563251 Unable to find the actual suspect from the above cl , @could someone please help us in finding the actual suspect. Thanks!
,
Jun 15 2017
I got the same problem on Win10 aswell, with 59.0.3071.86 (Offizieller Build) (64-Bit) (Kohorte: 59_86_Win)
,
Jun 16 2017
Suspecting Skia roll from the unregression range: https://chromium.googlesource.com/chromium/src/+/175ceeff6a099a7923928ba8fcd58c6b80563251
,
Jun 19 2017
I'm looking into the changes- let me get Brian on this in case he (or Mike) are aware of something they've changed lately in our color processing that could be the culprit.
,
Jul 31 2017
that working now for me with Version 60.0.3112.78 (Official Build) (64-bit)
,
Jul 31
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
,
Jan 11
This issue has an owner, a component and a priority, but is still listed as untriaged or unconfirmed. By definition, this bug is triaged. Changing status to "assigned". Please reach out to me if you disagree with how I've done this.
,
Jan 16
|
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by nils.ber...@gmail.com
, Jun 7 2017