CSS source map not recognized for blob
Categories
(DevTools :: Inspector, defect, P2)
Tracking
(Not tracked)
People
(Reporter: austaras, Unassigned)
References
(Blocks 1 open bug)
Details
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:67.0) Gecko/20100101 Firefox/67.0
Steps to reproduce:
use this repo, https://github.com/Austaras/boilerplate/tree/779e4baec70e0fb12f21f7ce2cd791ee91eb9d05
install all dependencies, run yarn run serve
Actual results:
CSS sourcemap not working
get an error in console TypeError: Invalid URL: .
Expected results:
CSS sourcemap should work
It only happens when CSS is referred through href="blob:xxxx"
, a separate file or inline CSS both works fine
Updated•6 years ago
|
Updated•6 years ago
|
Comment 2•6 years ago
|
||
Thanks for filing this bug.
I have installed the repo and built it (note that I had to remove the reference to the webp image in the html file as it was failing the webpack build otherwise since the image is missing).
I did reproduce the issue with the invalid sourcemap URL error in the console.
I tried debugging by adding a breakpoint to the sourcemap worker thread, but it seems like doing so crashes nightly for me!
Logan, I think you might help on this bug:
- Do you have an idea of where this bug might be coming from?
- Do you know if it needs to move to another bugzilla component, or maybe be turned into an upstream issue if this comes from the sourcemap lib?
Updated•6 years ago
|
Comment 3•6 years ago
|
||
I think this code:
has to be changed to support blob: as well as data:.
I feel like there used to be a bug for this somewhere, but I
couldn't readily find it.
Comment 4•6 years ago
|
||
Thank you Tom. So let me rephrase the question for Logan then:
what bugzilla component do sourcemap bugs usually belong to? Or do they get turned into github issues in the debugger.html repo isntead?
Comment 5•6 years ago
|
||
Generally sourcemap stuff is in the debugger component.
We have https://bugzilla.mozilla.org/show_bug.cgi?id=1538345 related to Blob URLs as well, but it doesn't looks like it is quite the same error message so probably best to just keep both issues for now.
Updated•6 years ago
|
Updated•6 years ago
|
Comment 6•5 years ago
|
||
This is the same core issue so closing as a dup.
Description
•