fix(@angular/cli): fix css url processing

[filipesilva]

Fixing component css in #4667 uncovered errors in CSS url processing.

This PR correctly composes absolute urls when using --base-href and/or --deploy-url.

It also fixes asset output on --aot mode. Thanks to @clydin for finding out assets were being dropped in the child compiler.

Fix #4778
Fix #4782
Fix #4806

[Brocco]

Nice work, LGTM!

[filipesilva]

Still having some problems with the eject config, I need to ask @hansl for advice on it next week.

[omargon]

@filipesilva thanks for the fix. Do you know when it will be release and/or if there is a workaround in the meantime?

[filipesilva]

@omargon workaround would be to use absolute image paths. This will come out next release, which should be early next week I think.

[omargon]

@filipesilva thanks.

[ghost]

I'm serving assets on a subdomain, and I need to set the deployUrl=http://sub.domain.com/, this worked on version beta26, but now with rc1 this is broken, and I think it is because of this fix you have done here.
In the generated code I see everywhere my deployUrl written like this: /http:/sub.domain.com/assets/...
It reads it as an absolute path relative to the url on which the files were served.

[clydin]

@es-lab please open an issue so that we can properly assist you.

[ghost]

@clydin I've opened the issue here #5254

[HelloPb]

background: url('assets/client/img.png') is throwing compilation error for ng build -prod

[angular-automatic-lock-bot]

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.}