UserAgent: Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/52.0.2743.116 Safari/537.36
Steps to reproduce the problem:
1. I've attached the files required to recreate this problem. However since Firefox doesn't seem to load sourcemaps from local files it's easier to use this link: https://dl.dropboxusercontent.com/u/17827955/chrome-sourcemaps/test.html
2. Inspect the red element in Chrome / Firefox / Edge / etc.
3. Chrome will say that the red background is coming from line 2 but all other browsers correctly say line 12.
4. Ruby sass and libsass generate different source mappings but both suffer the same bug in Chrome.
What is the expected behavior?
What went wrong?
Chrome points to the incorrect line in the source sass.
Did this work before? No
Chrome version: 52.0.2743.116 Channel: n/a
OS Version: 10.0
Flash Version: Shockwave Flash 22.0 r0
This was originally reported by someone else as a libsass bug: https://github.com/sass/libsass/issues/1783
|
Deleted:
test.html
159 bytes
|
|
|
Deleted:
test.css
108 bytes
|
|
|
Deleted:
test.css.map
156 bytes
|
|
|
Deleted:
test.scss
189 bytes
|
Comment 1 by chenwilliam@chromium.org
, Sep 17 2016Labels: -OS-Windows OS-All
Owner: lushnikov@chromium.org
Status: Assigned (was: Unconfirmed)