Skip to content

fix(overlay): centered flexible positioning not working in some browsers #10701

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

Merged

Conversation

crisbeto
Copy link
Member

@crisbeto crisbeto commented Apr 4, 2018

Currently using centering with the FlexibleConnectedPositionStrategy in flexible mode doesn't work in browsers that haven't implemented the new absolute position behavior inside a flex container (e.g. iOS Safari), which means that the position will be thrown off completely. These changes rework the position strategy to use position: static and justify-content/align-items, rather than position: absolute, to push the overlay pane to the proper edge of the bounding box in flexible mode. As a result, support for having flexible dimensions in only one direction has been removed.

@crisbeto crisbeto added the in progress This issue is currently in progress label Apr 4, 2018
@crisbeto crisbeto self-assigned this Apr 4, 2018
@googlebot googlebot added the cla: yes PR author has agreed to Google's Contributor License Agreement label Apr 4, 2018
@crisbeto crisbeto force-pushed the flexible-positioning-flexbox-fix branch 3 times, most recently from 0534dd6 to e8583d1 Compare April 7, 2018 11:10
Currently using centering with the `FlexibleConnectedPositionStrategy` in flexible mode doesn't work in browsers that haven't implemented [the new absolute position behavior inside a flex container](https://developers.google.com/web/updates/2016/06/absolute-positioned-children) (e.g. iOS Safari), which means that the position will be thrown off completely. These changes rework the position strategy to use `position: static` and `justify-content`/`align-items`, rather than `position: absolute`, to push the overlay pane to the proper edge of the bounding box in flexible mode. As a result, support for having flexible dimensions in only one direction has been removed.
@crisbeto crisbeto force-pushed the flexible-positioning-flexbox-fix branch from e8583d1 to 97b7446 Compare April 7, 2018 12:29
@crisbeto crisbeto changed the title wip(overlay): centered flexible positioning not working in some browsers fix(overlay): centered flexible positioning not working in some browsers Apr 7, 2018
@crisbeto crisbeto added pr: needs review and removed in progress This issue is currently in progress labels Apr 7, 2018
@crisbeto crisbeto assigned jelbourn and unassigned crisbeto Apr 7, 2018
@crisbeto crisbeto added the P1 Impacts a large percentage of users; if a workaround exists it is partial or overly painful label Apr 7, 2018
Copy link
Member

@jelbourn jelbourn left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@jelbourn jelbourn added pr: lgtm action: merge The PR is ready for merge by the caretaker target: patch This PR is targeted for the next patch release and removed pr: needs review labels Apr 9, 2018
@tinayuangao tinayuangao merged commit dfc3b02 into angular:master Apr 10, 2018
@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 8, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
action: merge The PR is ready for merge by the caretaker cla: yes PR author has agreed to Google's Contributor License Agreement P1 Impacts a large percentage of users; if a workaround exists it is partial or overly painful target: patch This PR is targeted for the next patch release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants