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

Issue 773235 link

Starred by 3 users

Issue metadata

Status: Fixed
Owner:
Last visit > 30 days ago
Closed: Jan 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows , Mac
Pri: 2
Type: Bug-Regression



Sign in to add a comment

Element will apply color from another style

Reported by ngl.ames...@gmail.com, Oct 10 2017

Issue description

UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/61.0.3163.100 Safari/537.36

Steps to reproduce the problem:
In a cycle, we create elements, for the background of one (4 element) of them we apply a style value different from the others, but color remains the same as the rest of the elements.
N.B.:Styles include opacity 
Example: http://semikolenov.ru/chrome/

What is the expected behavior?
In the example, the color of the 4 element must be red.

What went wrong?
The color of the 4 elements does not match the style

Did this work before? Yes 

Chrome version: 61.0.3163.100  Channel: stable
OS Version: 10.0
Flash Version: Shockwave Flash 27.0 r0
 
index.html
349 bytes View Download
test.js
759 bytes View Download
style.css
229 bytes View Download
Labels: Needs-Bisect Needs-Triage-M61

Comment 2 by junov@chromium.org, Oct 10 2017

Cc: junov@chromium.org
Labels: Needs-Feedback
Using Chrome 61.0.3163.100 on Windows 10, I am unable to reproduce this problem.  Are there any extra steps or configuration details that are required?
Version 61.0.3163.100 x64 Russian. I reproduce this problem on 3 Windows OS computers in office (10.10-1.png). After remote connect at home I see one more problem . 4 and later element have red background (10.10-2.png). This problem occurs very rarely in the office.
10.10-1.png
79.9 KB View Download
10.10-2.png
64.3 KB View Download
Project Member

Comment 4 by sheriffbot@chromium.org, Oct 10 2017

Labels: -Needs-Feedback
Thank you for providing more feedback. Adding requester "junov@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

Comment 5 by hdodda@chromium.org, Oct 11 2017

Cc: hdodda@chromium.org
Labels: -Needs-Bisect hasbisect-per-revision M-62 OS-Mac
Owner: enne@chromium.org
Status: Assigned (was: Unconfirmed)
Able to reproduce the issue on windows 10, mac os 10.12.6 using chrome latest beta M62 #62.0.3202.45 and M63 #63.0.3236.0 .

This is a regression issue broken in M62 and is not seen in linux.

Using the per-revision bisect providing the bisect results,
Good build: 62.0.3176.0 (Revision: 491883).
Bad build: 62.0.3177.0 (Revision: 492183).

You are probably looking for a change made after 491914 (known good), but no later than 491915 (first known bad).

CHANGELOG URL:

The script might not always return single CL as suspect as some perf builds might get missing due to failure.

 https://chromium.googlesource.com/chromium/src/+log/29eff3ab49027f70d179c783247568a3ffaacdac..e3d9eee91f3dfe5503bde5f3f4fc776e1552f857

From the CL above, assigning the issue to the concern owner 

@Adrienne Walker - Could you please check whether this is caused with respect to your change, if not please help us in assigning it to the right owner.

Reviewed-on: https://chromium-review.googlesource.com/596503

Thanks!

Comment 6 by enne@chromium.org, Oct 11 2017

Cc: enne@chromium.org
Owner: hdodda@chromium.org
hdodda: Can you retest this in 62.0.3202.45 and merge into 755871 if fixed?

Comment 7 by junov@chromium.org, Oct 11 2017

Components: -Blink Blink>Paint
Labels: -Needs-Triage-M61
Status: Fixed (was: Assigned)
Working correctly in M-64 and M-65.

Sign in to add a comment