Issue metadata
Sign in to add a comment
|
Source maps not working for less files
Reported by
m...@codeavengers.com,
Apr 3 2017
|
||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/59.0.3060.0 Safari/537.36 Steps to reproduce the problem: 1. Compile source maps with url's that start with file:// 2. Links in the elements css pane don't go to the file system resource anymore. What is the expected behavior? It should link to the file on the file system. What went wrong? It opened up a version with the url... localhost:/css/file:/... Did this work before? Yes Earlier today. Chrome version: 59.0.3060.0 Channel: n/a OS Version: 10.0 Flash Version:
,
Apr 4 2017
Could you please provide us the sample test file to triage the issue from TE End. Thanks in advance.
,
Apr 4 2017
I did provide a file?
,
Apr 4 2017
Thank you for providing more feedback. Adding requester "jmukthavaram@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 4 2017
It may have been because our source map paths had file:// instead of file:///
,
Apr 4 2017
It was working a few days ago with file:// so maybe something changed in Chrome that broke this?
,
Apr 4 2017
It is working now that we have changed it to file:///
,
Apr 5 2017
I'm just checking in to say that as of this morning, all of my SASS Sourcemaps aren't working. They're not auto-reloading the generated CSS after I save and compile locally. Was working up until yesterday, and nothing has changed on my end. Also looks like workspace mappings are prefixed with file:/// as well.
,
Apr 5 2017
,
Apr 6 2017
,
Apr 10 2017
@awesome.streak: are you on Chrome Canary? Could you share an example of how mappings don't work for you?
,
Apr 10 2017
,
Apr 12 2017
@lushnikov: Thanks for the response. After inspecting the issue further, my problem isn't the same as the topic, however I believe them to be linked. The main issue is that my CSS files do not auto-reload, upon being compiled (I use Compass [Ruby Gems]). For some reason, Chrome has stopped listening properly to these files, even though they are mapped to a file system resource. Downgrading to 56.0.2924.87 appears to have somewhat fixed the problem - the CSS does automatically reload upon being compiled, however this now happens very slowly (~5 seconds after the compile), compared to almost instantly reloading previously. In this version of Chrome I'm using (56.0.2924.87), I've also noticed that inspector no longer tells me which line and which SASS (.scss) file that the definition is based - it only tells me which line in the CSS (.css) file the definition is - which isn't useful obviously. Let me know if I can provide any more information - hopefully I explained it properly.
,
Apr 13 2017
It looks like your source maps don't get loaded properly. Could you please file a new bug (crbug.com/new) with a relevant details - your chrome version, and a reproduction steps so that we would be able to reproduce your behavior locally? Also, could you please check Chrome Canary to see if this works as expected there? We've done a huge refactoring related to source maps recently, which have fixed a lot of issues. Closing this bug since the topic issue seems to be fixed. |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by nyerramilli@chromium.org
, Apr 3 2017