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

fix(fxFlex): fix non-wrapping behavior and default fxFlex value #669

Merged
merged 1 commit into from
Mar 19, 2018

Conversation

CaerusKaru
Copy link
Member

@CaerusKaru CaerusKaru commented Mar 16, 2018

  • Set the non-wrapping behavior for fxFlex to be 100% instead of
    the width/height value
  • Set the default value for fxFlex to auto for column and 0% for
    row instead of 1e-9px

Fixes #666
Fixes #481
Fixes #544
Fixes #338
Fixes #314

@CaerusKaru CaerusKaru added this to the v6.0.0-beta.14 milestone Mar 16, 2018
@CaerusKaru CaerusKaru force-pushed the adam/fix-issue-481 branch 2 times, most recently from 78db2b1 to a46590c Compare March 16, 2018 08:32
@CaerusKaru
Copy link
Member Author

Note: confirmed issue with IE11 by removing the hack. Will consult Flexbugs and try to come up with an alternative that meets all requirements.

@CaerusKaru CaerusKaru force-pushed the adam/fix-issue-481 branch 2 times, most recently from 6dad8d3 to 0d1c306 Compare March 16, 2018 17:57
@CaerusKaru
Copy link
Member Author

Fixed the default value and officially unblocked

@ThomasBurleson
Copy link
Contributor

rebase this one also plz @CaerusKaru

* Set the non-wrapping behavior for fxFlex to be 100% instead of
  the width/height value
* Set the default value for fxFlex to auto instead of 1e-9px
@CaerusKaru
Copy link
Member Author

@ThomasBurleson done

@ThomasBurleson ThomasBurleson merged commit 3cfafd1 into master Mar 19, 2018
@CaerusKaru CaerusKaru deleted the adam/fix-issue-481 branch March 19, 2018 23:23
@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 5, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.