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 }}
This repository was archived by the owner on Nov 22, 2024. It is now read-only.
Repository navigation
This repository was archived by the owner on Nov 22, 2024. It is now read-only.
server side rendering of img src attribute within ngFor-collection coming from an http call #331
server side rendering should behave like client side rendering.
What is the motivation / use case for changing the behavior?
Please tell us about your environment:
Angular version: 2.0.0-beta.11
Browser: [all | Chrome XX | Firefox XX | IE XX | Safari XX ]
Language: [all | TypeScript X.X | ES6/7 | ES5 ]
OS: [all | Mac OS X | Windows | Linux ]
Platform: NodeJs
Other information (e.g. detailed explanation, stacktraces, related issues, suggestions how to fix, links for us to have context, eg. stackoverflow, gitter, etc)
changed the title [-]server side rendering of img src attribute resulting from an http call[/-][+]server side rendering of img src attribute within ngFor-collection coming from an http call[/+]on Mar 23, 2016
Activity
[-]server side rendering of img src attribute resulting from an http call[/-][+]server side rendering of img src attribute within ngFor-collection coming from an http call[/+]jeffwhelpley commentedon Apr 15, 2016
@lngr does
[src]work for you on the client side?lngr commentedon Apr 18, 2016
@jeffwhelpley yes
angular-automatic-lock-bot commentedon Sep 4, 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.