1415628 - CSS Source-Maps for LESS files no longer working after update to Firefox Developer Edition 58.0b1

Status: RESOLVED INVALID

(DevTools :: Style Editor, defect, P4)

Description

[michael.simonson]

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:58.0) Gecko/20100101 Firefox/58.0
Build ID: 20171103003834

Steps to reproduce:

I ran Gulp to process my LESS files with css source-maps. Before this update, they used to work fine. Now only see the .css fiies not the .less files.


Actual results:

CSS Source maps were generated, and they do work in the Firefox, just not Firefox Developer Edition.


Expected results:

Should be able to see the .less file sources.

Comment 1

[Tom Tromey :tromey]

I wrote a simple less example here:
https://tromey.github.io/source-map-examples/
This works for me using a recent-ish artifact build.

Can you try it and see if it works for you?
Direct link: https://tromey.github.io/source-map-examples/less/index.html

Also make sure you have the correct pref enabled.
It's available in the devtools options pane.

If that link does work for you, then I wonder what's different about your setup.
I used lessc --source-map-map-inline

Comment 2

[Tom Tromey :tromey]

Forgot to mark NI.

Comment 3

[michael.simonson]

Hi Tom Trommey,

I tried the links you gave me, and they do work. So maybe there is something wrong with our gulp tasks.
Working with my engineer to see what could be wrong. It is strange though, because we did not have any issues until the recent updates to Firefox/Firefox Developer Edition.

One thing tho, we generate separate css.map files for each less file. We do not inline our source maps. Is this required?

Comment 4

[Tom Tromey :tromey]

(In reply to michael.simonson from comment #3)

> One thing tho, we generate separate css.map files for each less file. We do
> not inline our source maps. Is this required?

No, that's not required.
What option are you using?  I could try that.

Comment 5

[Patrick Brosset <:pbro>]

See Tom's question above.

Comment 6

[michael.simonson]

HI All,

So we started in-lining our css source maps and now they work with Firefox.

Thanks to everybody who responded to this issue.

Comment 7

[Tom Tromey :tromey]

I'm not sure now if I should leave this open, as the original problem remains undiagnosed;
or close it as it seems unlikely now to figure it out.

Comment 8

[gregory]

I have the same problem for stylus files. I am using webpack. The styles all show up as "inline". Should I open a new bug? I have tried this on Firefox Developer Edition (59.0b13) and regular Firefox (58.0.2). In Chrome the styles are shown. I'll upload a screenshot of the two.

Comment 9

[gregory]

Attachment: 2018-03-02_11-02-09.png

Chrome vs firefox dev tool for css source maps

Comment 10

[Tom Tromey :tromey]

(In reply to gregory from comment #8)
> I have the same problem for stylus files. I am using webpack. The styles all
> show up as "inline". Should I open a new bug? I have tried this on Firefox
> Developer Edition (59.0b13) and regular Firefox (58.0.2). In Chrome the
> styles are shown. I'll upload a screenshot of the two.

Can you say how to modify the test case from comment #1 to show the bug?
That would be very helpful.
The sources are here https://github.com/tromey/source-map-examples if that helps.

Comment 11

[Logan Smyth [:loganfsmyth]]

This does not appear to have any repro steps and has been waiting for info for 2 years so I'm going to close it.