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

Issue 641099 link

Starred by 1 user
Status: WontFix
Owner:
█ lushnikov@chromium.org
Last visit 29 days ago
Closed: Dec 2017
Cc:
l...@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

DevTools: shadow DOM related property traces in computed styles do not appear when selecting shadow's content

Project Member Reported by l...@chromium.org, Aug 25 2016 
Version 54.0.2836.0

What steps will reproduce the problem?
(1) Create a page with shadow DOM, where the outer light DOM has some style (e.g. white-space: pre-wrap) and the shadow DOM has some conflicting style (e.g. white-space: nowrap). 
(2) Open elements panel in DevTools and select the <content> element
(3) In the computed styles sidebar, expand the style that conflicts.  It should show the shadow's style
(4) Now select elements inside of <content>.  The trace is gone!
Screen Shot 2016-08-25 at 12.47.19 PM.png
359 KB View Download
Screen Shot 2016-08-25 at 12.47.33 PM.png
348 KB View Download

Comment 1 by dtapu...@chromium.org, Aug 30 2016

Components: Platform>DevTools

Comment 2 by lushnikov@chromium.org, Dec 5 2017

Status: WontFix (was: Assigned)
This is indeed the case. Traces are computed manually from the matched styles. In case of distributed light dom, the matched styles are not combined with the shadowtree styles - thus the results.

Given that:
- this is a pretty rare case
- addressing this would require re-architecturing styles on the front-end

I'm closing for now.
►

Sign in to add a comment