Thanks for filing the issue!

@Reporter: If possible could you please provide sample Test File/URL that reproduces the issue which help in further triaging it in better way. If possible could you please provide screencast or screenshot of the issue which help in better understanding.

Thanks!

Correction: Files should be compiled with Web Essentials (not WebCompiler) to reproduce the issue. See attached examples for maps failing to parse.

Deleted: fails.scss 40 bytes

fails.scss 40 bytes Download

Deleted: fails.css 75 bytes

fails.css 75 bytes View Download

Deleted: fails.css.map 171 bytes

fails.css.map 171 bytes Download

Deleted: succeeds.css.map 168 bytes

succeeds.css.map 168 bytes Download

Thank you for providing more feedback. Adding the requester to the cc list.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Tried testing the issue on chrome reported version# 72.0.3599.0 using Windows-10 with steps mentioned below:
1) Launched chrome reported version and downloaded all the files provided in comment# 3 and placed in one folder
2) Ran a local server with port 8000 and navigated to folder created in first step
3) Clicked on fails.css, and opened Devtools> Console, didn't seen any error messages in console tab and clicked on Sources tab, able to only fails.css in it

@Reporter: Please find the attached screencast and provide your feedback on it. If possible could you please provide the screencast of the issue which help in better understanding and further triaging it in better way.

Thanks!

Deleted: 900923.mp4 3.2 MB

	900923.mp4 3.2 MB View Download

Sourcemap is needed to display the original source (the content of .scss file) in the "Sources", so a successful test would add the .scss file to the "Sources" tab (see right side of "compare.jpg").

You're not getting an error, because the CSS file is not included in an HTML document, so Chrome won't try to parse it. Please try to reproduce this issue through the following steps:

1. Download "fails.css" and "fails.css.map"
2. Start a local webserver that serves an HTML document containing at least an "html", "head" and a "body" tag
3. Include the "fails.css" in a "link" tag under the "head" tag
4. Request the page with Chrome 72.0.3599.0

If it fails, "fails.scss" will NOT be in the sources (see left side of "compare.jpg"), if it succeeds, it should be there (see the right side).

Thank you for providing more feedback. Adding the requester to the cc list.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Tried testing the issue on chrome reported version# 72.0.3599.0 using Windows-10 with steps mentioned in comment# 7
1) Downloaded "fails.css" and "fails.css.map" files provided in comment# 3 and placed it in one folder
2) Created a '.html' file where we have included "fails.css" in a "link" tag under the "head" tag(find attached for the same)
3) Ran a local server with 8000 port, and opened the file created in above step, observed "Not allowed to load local resource" error message in Devtools>Console tab
Observations: Also tried testing the issue by directly dropping the '.html' file in to new tab, observed "DevTools failed to parse SourceMap" warning message in Devtools>Console tab

@Reporter: Please find the attached screencast for your reference and let us know if we missed anything in reproducing the issue, provide you feedback on it which help in further triaging it in better way.

Thanks!

Deleted: 900923.html 148 bytes

900923.html 148 bytes View Download

Deleted: 900923.mp4 4.5 MB

	900923.mp4 4.5 MB View Download

Yes, that's exactly the behavior I got (the warnings, not the "failed to load" errors, those are probably from a misconfigured webserver).

You indeed don't need a webserver to reproduce the issue, as Chrome will parse the CSS from a static HTML document too.

Thank you for providing more feedback. Adding the requester to the cc list.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Able to reproduce the issue on chrome reported version# 72.0.3599.0, latest stable# 70.0.3538.77 and on latest chrome# 72.0.3604.0 using Windows-10, Mac 10.12.6 and Ubuntu 14.04 with steps and sample file provided in comment# 9. As this issue is seen from M-60(60.0.3112.0), hence considering this issue as Non-Regression and marking it as untriaged.

Thanks!

 Issue 915356  has been merged into this issue.

We also noticed this. Turns out chrome 70 sent cookies for the map file requests (we had all requests behind an auth guard on the server) but 71 no does not send cookies which caused our auth middleware to fail.