Skip to content
This repository has been archived by the owner on Jan 6, 2025. It is now read-only.

using fxLayoutGap does not consider children fxFlex? #242

Closed
mackelito opened this issue Mar 29, 2017 · 5 comments
Closed

using fxLayoutGap does not consider children fxFlex? #242

mackelito opened this issue Mar 29, 2017 · 5 comments
Labels
P4 Low-priority issue that needs to be resolved

Comments

@mackelito
Copy link

mackelito commented Mar 29, 2017

Might be me using this in the wrong way but here we go...
using fxLayoutGap together with fxFlex="33" results a broken layout

screen shot 2017-03-29 at 9 04 49 am

https://plnkr.co/edit/uGK8xUVyHbjGvjEqbDci?p=preview

I guess this can be solved by setting it all in % like fxLayoutGap="3%" fxFlex="30%"... but what if I want flex in 33% and then a 8px gap?

@ThomasBurleson
Copy link
Contributor

ThomasBurleson commented Mar 29, 2017

fxLayoutGap adds a margin-right for layout="row" and margin-bottom for layout="column" to all content children.

All values default to percentages unless a trailing px is specified; e.g.

  • fxFlex="33px"
  • fxFlex="47" === 47%

What layout are you trying to achieve (picture plz)?

@mackelito
Copy link
Author

The "issue" is when using fxLayoutWrap.
In the image you see that we have 2 items per rows.. but it should be 3 per row when using 33% right?

@mackelito
Copy link
Author

I just saw this discussion #165 and think it might be the same issue I´m having..

@fxck
Copy link

fxck commented Mar 31, 2017

@mackelito #134 would this solve your problem?

@ThomasBurleson ThomasBurleson added the P4 Low-priority issue that needs to be resolved label Jun 22, 2017
@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
P4 Low-priority issue that needs to be resolved
Projects
None yet
Development

No branches or pull requests

3 participants