-
Notifications
You must be signed in to change notification settings - Fork 773
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
fxLayoutGap not applied to children inserted after initial render #95
Comments
Definitely an oversight. We will fix. Thx |
@drew-moore - this issue is non-trivial to solve since the The only other current option is to watch with a MutationObserver.
@pkozlowski-opensource - any thoughts |
* fxLayoutGap not applied to children inserted after initial render Fixes #95.
* fxLayoutGap not applied to children inserted after initial render Fixes #95.
* fxLayoutGap not applied to children inserted after initial render Fixes #95.
@drew-moore - see pending Pull Request #124 |
* fxLayoutGap not applied to children inserted after initial render Fixes #95.
* fxLayoutGap not applied to children inserted after initial render Fixes #95.
* fxLayoutGap not applied to children inserted after initial render Fixes #95.
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
Plunk.
When a container with a layout gap has a child that isn't present initially (e.g. has an ngIf condition that evaluates to false), the gap is not applied to the child when it is subsequently inserted.
Worth noting: layoutAlign is working as expected (presumably because alignment is implemented via a rule on the parent whereas gaps are implemented as margins on the children, which isn't happening for children added after the initial layout computation).
The text was updated successfully, but these errors were encountered: