You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Css sourcemaps are not loaded / displayed when using styleUrls: [...] #9664
Current behavior
When using the styleUrls to load a stylesheet with ecapsulation: ViewEncapsulation.None it does not properly load the sourcemap that is associated with it. Nor does it work when using inline css sourcemaps.
Expected/desired behavior
It should within the browser show the sourcemap of the css when opening the development tools. Just like it does when you use sourcemaps normally within inline <style> tags.
Reproduction of the problem
Within the plunker example below you can see that the native implementation works yet when the style is specified using:
@Component({selector: 'my-app',moduleId: __moduleName,styleUrls: ['style.css'],encapsulation: ViewEncapsulation.None,providers: [],template: `<div class="test"> I should be blue </div>`})exportclassApp{
It no longer works and the source map is not linked to the css that is inlined.
What is the motivation / use case for changing the behavior?
This would make it possible to more easily include style sheets for specific routes while making sure a Frontend designer can alter the sass without requiring him/her to constantly search for the sass that is associated with the inline css.
Activity
vicb commentedon Jun 28, 2016
@tbosch any plan to support this ?
asnowwolf commentedon Aug 12, 2016
@vicb
This issue is related to
https://github.com/angular/angular/blob/master/modules/%40angular/compiler/src/shadow_css.ts#L460
I'll try to fix it.
asnowwolf commentedon Aug 12, 2016
I think this issue is important.
asnowwolf commentedon Aug 12, 2016
Sorry, I can't run CI scripts on my dev env. So I have to trigger remote CI to valid the commits.
fix(core): don't strip sourceMappingURL (#9664)
angular-automatic-lock-bot commentedon Sep 9, 2019
This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.
Read more about our automatic conversation locking policy.
This action has been performed automatically by a bot.