New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 730489 link

Starred by 2 users

Issue metadata

Status: Fixed
Owner:
Closed: Jan 16
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 2
Type: Bug-Regression


Participants' hotlists:
Hotlist-1


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 description

UserAgent: 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:
 
Bildschirmfoto 2017-06-07 um 12.00.50.png
13.2 KB View Download
Bildschirmfoto 2017-06-07 um 12.06.49.png
9.4 KB View Download
Here is also a jsfiddle to show the problem and that it only occurs with the exact same rgba values - https://jsfiddle.net/ybx2fdqp/1/
Labels: Needs-Triage-M59 Needs-Bisect

Comment 3 Deleted

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!

Comment 5 by lgrey@google.com, Jun 9 2017

Components: Blink>CSS
[Mac triage] Over to Blink, though FWIW, this doesn't repro for me in either stable or Canary with the given JSFiddle
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.
2017-06-10 00_19_41-.png
92.4 KB View Download
here you ll find a picture with v58 in the same condition.



2017-06-10 01_06_35-.png
98.6 KB View Download
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.

Comment 9 Deleted

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.
2017-06-11 15_48_37-.png
89.0 KB View Download
Cc: hdodda@chromium.org
Labels: Needs-Feedback
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!
M58Behavior-730489.png
196 KB View Download
M59Behavior-730489.png
189 KB View Download

Comment 12 Deleted

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.
@hdodda@chromium.org

Yep the 58 is how it should look, correct.
Project Member

Comment 15 by sheriffbot@chromium.org, Jun 14 2017

Labels: -Needs-Feedback
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
Labels: -Needs-Bisect M-60 hasbisect
Status: Untriaged (was: Unconfirmed)
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!
I got the same problem on Win10 aswell, with 59.0.3071.86 (Offizieller Build) (64-Bit) (Kohorte: 59_86_Win)

Components: -Blink>CSS Internals>Skia
Status: Available (was: Untriaged)
Suspecting Skia roll from the unregression range:
https://chromium.googlesource.com/chromium/src/+/175ceeff6a099a7923928ba8fcd58c6b80563251

Comment 19 by hcm@chromium.org, Jun 19 2017

Cc: hcm@chromium.org reed@google.com
Owner: brianosman@chromium.org
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.
that working now for me with Version 60.0.3112.78 (Official Build) (64-bit)
Project Member

Comment 21 by sheriffbot@chromium.org, Jul 31

Labels: Hotlist-Recharge-Cold
Status: Untriaged (was: Available)
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
Status: Assigned (was: Untriaged)
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.
Status: Fixed (was: Assigned)

Sign in to add a comment