New issue
Advanced search Search tips

Issue 751728 link

Starred by 3 users

Issue metadata

Status: WontFix
Owner:
Closed: Dec 2017
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug



Sign in to add a comment

shows warning about /deep/ when it doesn't occur

Reported by davidmax...@gmail.com, Aug 2 2017

Issue description

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

Steps to reproduce the problem:
1. not sure - it seems pretty random

What is the expected behavior?
I expect warnings about using /deep/ when I actually use /deep/ and for the warnings to point to lines where it is actually used.

What went wrong?
It shows warnings where /deep/ isn't used and points to a line where /deep/ doesn't occur and it's even related.

Did this work before? N/A 

Chrome version: 59.0.3071.115  Channel: n/a
OS Version: 10.0
Flash Version:
 
deep-dev-tool-error.PNG
21.4 KB View Download
Owner: l...@chromium.org
Status: Assigned (was: Unconfirmed)

Comment 2 by l...@chromium.org, Aug 3 2017

Labels: Needs-Feedback
Thanks for the report.  Would you be able to provide a sample of code/jsfiddle for us to reproduce?  I wasn't able to get a warning when triggered from a script at all.

Also,
- Is the line triggering the /deep/ violation somewhere else in the same file?
- Is the file being sourcemapped?
Sorry, I can't help you there. It seems totally random from my point of view, and I don't use /deep/ at all. IIRC, that line is in one of the paper polymer elements...yes, paper-spinner:

https://github.com/PolymerElements/paper-tooltip/blob/master/paper-tooltip.html#L248

but it happens elsewhere too. /deep/ does occur in some of the polymer layout files, iirc, and chrome warns me about those, though I don't actually use anything that uses /deep/ (I only use the flexbox mixins).

Anyway, the point is not that /deep/ is used or not, but that it is pointing at a line that is totally nothing to do with /deep/. I've become used to completely ignoring all such warnings.

Comment 4 by l...@chromium.org, Aug 14 2017

 Issue 754602  has been merged into this issue.
Status: WontFix (was: Assigned)
No repro

Sign in to add a comment