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

verticalAlignment in a nested track gets assigned a value from an ancestor track instead of the default value #220

Open
certainlyakey opened this issue Feb 5, 2024 · 0 comments
Labels
bug Something isn't working

Comments

@certainlyakey
Copy link
Contributor

certainlyakey commented Feb 5, 2024

What happened?

In a consumer app template that uses nested cvi-ng-track, if verticalAlignment is set to any value in an ancestor track, then a child track without verticalAlignment set will inherit the value of its parent.

Expected result: unset verticalAlignment in a nested track should result in align-items: normal; instead of inheriting the value of an ancestor track.

Reproduction steps

Use this template to reproduce:

<cvi-ng-track [gap]="6" [flexDirection]="'horizontal'" [horizontalAlignment]="'justify'" [verticalAlignment]="'bottom'">
  <cvi-ng-track [gap]="4" horizontalAlignment="normal" [flexDirection]="'vertical'">
    <div>Water choice sky luck scientific thee through pull beyond bent especially gasoline top close stared she this strange explain success nuts coat morning club. Burst reader popular cat promised angle throw came sign electric long action mother structure break pretty does bigger thought ill middle poor becoming partly</div>
    <cvi-ng-button>Lähen nõusolekut andma</cvi-ng-button>
  </cvi-ng-track>
  <img src="https://upload.wikimedia.org/wikipedia/commons/a/a9/Williamsburgh_Savings_Bank_Tower_9128_crop.JPG" width="30" height="100" />
</cvi-ng-track>

Screenshot

No response

Package

Angular

Version

2.8.0

Reproduction URL

No response

Browser

No response

Browser version

No response

Extra details about your environment

No response

Relevant log output

No response

@certainlyakey certainlyakey added the bug Something isn't working label Feb 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant