Reading source maps files not working in Canary but working in Chrome
Reported by
stevenle...@gmail.com,
Apr 12 2017
|
|||||||||||||||||||||
Issue description
Chrome Version : 59.0.3068.1
OS Version: OS X 10.12.4
URLs (if applicable) : hosted locally through Tomcat 7 using HTTPS.
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?
1. Evaluating styles that are compiled using scss and sourcemaps.
Canary uses the black background in the devtools.
Chrome uses the white background in the devtools.
In the first screenshot you can see Canary and Chrome side by side with the devtools opened to the same local page. Connecting thru a browser-sync proxy port 3000.
In the canary devtools with the <body> tag selected you can see in the Styles tab the core.css is referenced. Connecting thru a browser-sync proxy port 3000. Also notice my javascript files I have sourcemapped are referencing jquery.min.js
In the chrome devtools with the <body> tag selected you can see in the Styles tab _typography.scss is referenced. In the console the same minfied and sourcemap javascript files are referencing jquery.js.
In the second screenshot you can see canary is now using the same page but not going thru the proxy but going directly to the tomcat secure port 8443. You can see the Styles tab is still referencing the core.css file. But the javascript that has been min and sourcemapped is getting picked up! jquery.js is getting read but not the scss maps.
I've used the "Restore defaults and Reload" along with restart. Doesn't work.
I've also done the Clear browsing data > Cached images and files to make sure nothing is cached.
What is the expected result? To see the _typography.scss referenced from the sourcmaps.
What happens instead of that? Canary isn't detecting the sourcemaps.
Please provide any additional information below. Attach a screenshot if
possible.
UserAgentString: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/59.0.3068.1 Safari/537.36
,
Apr 13 2017
stevenleija@ - Thanks for filing the issue...!! Could you please provide a sample URL to test this issue. This will help us in triaging the issue further. Thanks...!!
,
Apr 13 2017
krajshree - unfortunately this is ran on my local server and my client won't condone me putting up a repo or test site of the code. It's very odd is runs just fine in Chrome. I've only seen the "Restore defaults and reload" work once in the hundreds of times I've tried to get this working. Any suggestions or additional screenshots I can provide that could help?
,
Apr 13 2017
Thank you for providing more feedback. Adding requester "krajshree@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
,
Apr 13 2017
,
Apr 17 2017
We would need much more details here. First thing first - could you open devtools on devtools and check for any errors in console? Next, is it possible that you provide us with your css sources - both compiled CSS files and sourcemap? Is there any chance you can build a repro case which illustrates the issue and which you would be able to share with us? This would drastically speedup fixing this.
,
Apr 19 2017
ok, I've attached the compiled code. I've attached a screenshot. Canary Chrome has the black devtools background. Chrome has the white background dev tools. You can see there are error but they are just missing images files and a 3rd party library fail. They are present in all the screenshots. The white devtools illustrates the map files working on port 3000 but failing on the same port in Canary.
,
Apr 19 2017
And the last screenshot shows which css files are being loaded for confirmation from attached zip files.
,
May 18 2017
Can we have the latest update on this issue?
,
May 18 2017
It looks like part of the issue has been resolved. From the screenshots you can see that the sourcemaps for javascript files are now being read in. You can see homepage-2.0.0.js is now being read verses homepage-2.0.0.min.js. The sass sourcemaps are not being read in correctly. You can see the .css files in the normal port and the .scss maps in the proxied url. Version 60.0.3103.0 (Official Build) canary (64-bit)
,
May 18 2017
In addition it appears that the scss sourcemaps is now broken in regular Google Chrome. Version 58.0.3029.110 (64-bit)
,
May 24 2017
This issue seems to be out of TE-scope. Hence, adding label TE-NeedsTriageHelp for further investigation. lushnikov@ - Could you please have a look into this issue. Thanks...!!
,
May 24 2017
Removing from bisect bucket.
,
May 26 2017
Question. If running both Canary and Chrome at the same time is there any conflict between the two with developer tools? Cache? Settings?
,
May 31 2017
Is there any response to my last question?
,
Dec 10 2017
What's the status of this? Do sourcemaps work for you on Chrome 63 / 65?
,
Dec 20 2017
,
Dec 20 2017
When Chrome Canary updated to v65, I had to roll back to normal Chrome in order to get source mapping working correctly. It seems v63/65 has removed the ability to 'map to network resource'. Recently, Chrome upgraded to v63 (from 62) and broke the source mapping again. I'm currently running a downgraded version of Chrome (to 62) in order to retain source mapping. |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by ligim...@chromium.org
, Apr 12 2017