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

Issue 657384 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 452542
Owner: ----
Closed: Nov 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Chrome , Mac
Pri: 2
Type: Bug



Sign in to add a comment

CSS precedence is changed after removal of ::shadow pseudo element from CSS rule

Project Member Reported by sidharam...@synerzip.com, Oct 19 2016

Issue description

System Information

Operating System:Linux x86_64
Chrome Browser Version: 54.0.2840.59
Chrome OS Version: 4
CPU: Intel(R) Core(TM) i5-5200U CPU @ 2.20GHz ( x86_64architecture - 4 processors )
Memory: 8.13GB available out of 16.73GB

jsFiddle link - https://jsfiddle.net/sidharamteli/xa4hsk4h/

What steps will reproduce the problem?
(1)Open attached jsfiddle link.
(2)Observe table cell border.
(3)Remove the '.div1::shadow > p' CSS rule.
(4)Observe table cell border

What is the expected output?
CSS for table cell border should not affect.

What do you see instead?
CSS for table cell border is affected.


As ::shadow pseudo element is deprecated, I want to remove it from css rule. 
You can see the discussion here - https://groups.google.com/a/chromium.org/forum/#!msg/blink-dev/68qSZM5QMRQ/pT2YCqZSomAJ 

 

Comment 1 by hlo@chromium.org, Oct 26 2016

Cc: hlo@chromium.org
Components: Blink>CSS

Comment 3 by r...@opera.com, Nov 9 2016

Cc: hayato@chromium.org kochi@chromium.org
Mergedinto: 452542
Status: Duplicate (was: Untriaged)
This is a duplicate of  issue 452542 . That is marked as a duplicate of a bug which is marked as fixed, but it's fixed by implementing the cascade order correctly in shadow dom v1. The v0 shadow (createShadowRoot, not attachShadow) cascading order is still broken, and we decided not to spend a lot of time trying to fix it, IIRC.

Comment 4 by r...@opera.com, Nov 9 2016

Correction: I tried to fix it, but there was too much shadow dom v0 content relying on this broken cascading order. See https://bugs.chromium.org/p/chromium/issues/detail?id=452542#c12

Sign in to add a comment