Skip to content
This repository was archived by the owner on Nov 22, 2024. It is now read-only.
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

Closed

Description

@lngr
  • I'm submitting a ...
  • bug report
  • feature request
  • Do you want to request a feature or report a bug?

bug

  • What is the current behavior?

the src attribute on the <img> tag is not rendered within a *ngFor if the *ngFor loops over a collection that is fetched via ajax.

If attr.src is used, it works just fine.

On client rendering, both methods work just fine.

  • If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem by creating a github repo.

see https://github.com/lngr/angular-universal-ssr-img-bug

  • What is the expected behavior?

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)

Activity

  1. 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
  2. self-assigned this
    on Mar 28, 2016
  3. jeffwhelpley commented on Apr 15, 2016

    @jeffwhelpley
    Contributor

    @lngr does [src] work for you on the client side?

  4. lngr commented on Apr 18, 2016

    @lngr
    Author
  5. angular-automatic-lock-bot commented on Sep 4, 2019

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

  6. locked and limited conversation to collaborators on Sep 4, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions