Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bug (or expected behavior) when i add items to existing fxLayout or use HTTP with *ngFor #128

Closed
oshri551 opened this issue Jan 24, 2017 · 5 comments

Comments

@oshri551
Copy link

I tried to use fxLayout="column" with fxLayoutGap

I get my appDetails via object http get, the expected behavior is that there will be 10px gap between the items, but there is no gap.

<div fxLayoutAlign="start center" fxLayout="column" fxLayoutGap="10px">
   <button *ngFor="let action of appDetails.Actions" md-raised-button color="primary"   
   {{action.ActionName}}
   </button>
</div>

What i did to replicate it is to create static array with few items and then use the *ngFor to show them and that works (but it's not async) so i made a button to add items to the array, those items rendered without the fxLayoutGap.

I made plunker based on the plunker template

You can see the items that were before in the array rendered perfectly, but if i add new item it rendered without to flexLayoutGap (same for row and column)

@joshwiens
Copy link
Contributor

joshwiens commented Jan 24, 2017

@oshri551 See - #95

@ThomasBurleson
Copy link
Contributor

@oshri551 - this has been fixed in #master and will be available on npm in the upcoming Beta.4.

See fixes here: #124

1 similar comment
@ThomasBurleson
Copy link
Contributor

@oshri551 - this has been fixed in #master and will be available on npm in the upcoming Beta.4.

See fixes here: #124

@oshri551
Copy link
Author

@ThomasBurleson It works perfectly now, thanks!

@angular-automatic-lock-bot
Copy link

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.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Sep 4, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants