This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 241097 - Sass source maps do not work in Chrome 32
Summary: Sass source maps do not work in Chrome 32
Status: VERIFIED FIXED
Alias: None
Product: web
Classification: Unclassified
Component: Inspection (show other bugs)
Version: 8.0
Hardware: All All
: P3 normal (vote)
Assignee: Jan Stola
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-01-29 09:12 UTC by Vladimir Riha
Modified: 2014-07-08 14:47 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
webkit log (83.43 KB, text/x-log)
2014-01-29 09:12 UTC, Vladimir Riha 		Details
IDE log (34.84 KB, text/x-log)
2014-01-29 09:13 UTC, Vladimir Riha 		Details
sample project (3.85 KB, application/zip)
2014-01-29 09:13 UTC, Vladimir Riha 		Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Vladimir Riha 2014-01-29 09:12:54 UTC 
Created attachment 144506 [details]
webkit log

Please try:
 - open attached project
 - make sure Sass compiler is set up and modify scss/newstyle.scss and save it
 - css file is recompiled
 - run it in Chrome with NB integration (chrome version see below)
 - in Browser DOM window, select <div> element

=> CSS Styles window no longer indicates that the color property comes from Sass file:
  - in Applied styles, it shows newstyle.css:0 as origin of the "div" rule
  - tooltip texts in Properties and Applied Styles section point to CSS file
  - Rule editor section is missing the red label saying that the property comes from compiled source
  - BUT Go To Declaration opens Sass file as expected.

The same works in embedded browser and in Chromium (see below)



Chromium: Version 31.0.1650.63
Chrome: Version 32.0.1700.77


Product Version: NetBeans IDE Dev (Build 201401290001)
Java: 1.8.0-ea; Java HotSpot(TM) Client VM 25.0-b66
Runtime: Java(TM) SE Runtime Environment 1.8.0-ea-b125
System: Linux version 3.2.0-48-generic-pae running on i386; UTF-8; en_US (nb)
Comment 1 Vladimir Riha 2014-01-29 09:13:09 UTC 
Created attachment 144507 [details]
IDE log
Comment 2 Vladimir Riha 2014-01-29 09:13:41 UTC 
Created attachment 144508 [details]
sample project
Comment 3 Jan Stola 2014-04-25 13:58:20 UTC 
I am able to reproduce this problem using Chrome 34 and NetBeans 8.0. On the other hand, this works correctly in the latest development build.

The root of this problem was the same as the root of issue 241098. The search for the mapping between the generated CSS file and SASS file failed because of the missing source line information (caused by the change in the protocol).

> BUT Go To Declaration opens Sass file as expected.

Yes, this is surprising at the first sight, but Go To Declaration uses a bit different algorithm than the other mentioned areas of web inspection. Go To Declaration, being a not very frequent explicit user action, uses a more heavy-weight algorithm with some heuristics (solving various bugs in various WebKit versions). Hence, it works even in this situation.

I am marking this issue as fixed because it was fixed together with issue 241098.
Comment 4 Vladimir Riha 2014-07-08 14:47:56 UTC 
Thank you, verified

NetBeans IDE Dev (Build 201407080001)