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

Issue 604074 link

Starred by 2 users

Issue metadata

Status: Duplicate
Merged: issue 356999
Owner:
Last visit 29 days ago
Closed: Aug 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Mac
Pri: 2
Type: Bug-Regression



Sign in to add a comment

Inconsistent information in style panel: more than one conflicting rules not striked

Reported by teo8...@gmail.com, Apr 15 2016

Issue description

Chrome Version       : 49.0.2623.112
OS Version: 
URLs (if applicable) :
Other browsers tested:
  Add OK or FAIL after other browsers where you have tested this issue:
     Safari 5:
  Firefox 4.x:
     IE 7/8/9:

What steps will reproduce the problem?

The screenshot should be enough to demonstrate that there's a bug

What is the expected result?

When there are different rules that assign values to the same property, there should never, ever be more than one that is not striked. 

What happens instead of that?

There are three non-striked rules assigning values for the property "color".

Please provide any additional information below. Attach a screenshot if
possible.

UserAgentString: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/49.0.2623.112 Safari/537.36



 
Screenshot from 2016-04-15 18-33-26.png
33.2 KB View Download
Cc: rnimmagadda@chromium.org
Labels: Needs-Feedback
@teo8976: Could you please have a look at the attached screen-shot at let us know if this is the behavior you were expecting.

Also, update your Google Chrome to Latest Stable Version - 50.0.2661.75 and let us know your observations.

Thank you.
604074.png
124 KB View Download

Comment 2 by teo8...@gmail.com, Apr 21 2016

Well, the attached screenshot seems to exhibit expected behavior, but it doesn't seem to be a test case at all. 

Comment 3 by teo8...@gmail.com, Apr 21 2016

So, I have done your job and here's a simple test example that could be easily created with the information provided in my report:

http://output.jsbin.com/colili
Project Member

Comment 4 by sheriffbot@chromium.org, Apr 21 2016

Labels: -Needs-Feedback Needs-Review
Owner: rnimmagadda@chromium.org
Thank you for providing more feedback. Adding requester "rnimmagadda@chromium.org" for another review and adding "Needs-Review" label for tracking.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Labels: -Needs-Review Needs-Bisect
Cc: vsevik@chromium.org pfeldman@chromium.org
Components: Blink>CSS
Labels: -Type-Bug -Pri-3 -Needs-Bisect M-50 OS-Mac OS-Windows Pri-2 Type-Bug-Regression
Owner: lushnikov@chromium.org
Status: Assigned (was: Unconfirmed)
====================================

Good Build:

40.0.2172.0    Base Position: 297115


Bad Build:

40.0.2214.0    Base Position: 303346

=====================================

Able to repro this issue on Windows 7, MAC (10.11.4) & Ubuntu Trusty (14.04) for the Google Chrome Stable Version - 50.0.2661.87

This is a regression issue broken in M40, below mentioned is the bisect info:

CHANGELOG URL: https://chromium.googlesource.com/chromium/src/+log/f060c7830b664e74b14d10b3ddb248f3438945a5..f7c35ac13ba449f1bbed646270435f9c9e6d97b0

https://chromium.googlesource.com/chromium/src/+/2ad554887364b56d709d031eff0b38b39801fa08

https://chromium.googlesource.com/chromium/blink/+log/3ea7c10ceb44449d5d1c8403a5953d4f24bcd8a9..97cb3f8ea7c73636fdb662a8fe6aef86344e350

https://chromium.googlesource.com/chromium/blink/+/065a6b123285b824b0f434d9b169cb6a8d0f5e41

Suspecting Commit: 065a6b123285b824b0f434d9b169cb6a8d0f5e41			

Review URL: https://codereview.chromium.org/699873002

@lushnikov: Could you please look into the issue, and if it has nothing to do with your changes and if possible please do assign it to the concerned owner.

Thank you.

Comment 7 by timloh@chromium.org, Apr 26 2016

Components: -Blink>CSS Platform>DevTools>HTML
Mergedinto: 356999
Status: Duplicate (was: Assigned)
Styles Sidebar does not support link pseudo-classes properly (such as :active)

Sign in to add a comment