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

fix(connected-position-strategy): wrong logic when determining whether element is on screen #2677

Merged
merged 1 commit into from
Jan 18, 2017

Conversation

crisbeto
Copy link
Member

Fixes some faulty logic, introduced in #2102, that meant that the overlay considers the viewport's scroll offset when determining how much it overflows on either side.

Fixes #2658.

…r element is on screen

Fixes some faulty logic, introduced in angular#2102, that meant that the overlay considers the viewport's scroll offset when determining how much it overflows on either side.

Fixes angular#2658.
@googlebot googlebot added the cla: yes PR author has agreed to Google's Contributor License Agreement label Jan 16, 2017
@jelbourn
Copy link
Member

Don't you want to account for the scroll?

@crisbeto
Copy link
Member Author

crisbeto commented Jan 17, 2017

Nope, this is relative to the viewport, not the page itself. I didn't really notice it testing locally, because our demo app uses md-sidenav-layout.

@jelbourn
Copy link
Member

LGTM

@jelbourn jelbourn added pr: lgtm action: merge The PR is ready for merge by the caretaker and removed pr: needs review labels Jan 17, 2017
@mmalerba mmalerba merged commit e055d05 into angular:master Jan 18, 2017
kara pushed a commit to kara/material2 that referenced this pull request Jan 20, 2017
…r element is on screen (angular#2677)

Fixes some faulty logic, introduced in angular#2102, that meant that the overlay considers the viewport's scroll offset when determining how much it overflows on either side.

Fixes angular#2658.
@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 6, 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
Projects
None yet
Development

Successfully merging this pull request may close these issues.

md-menu open on the bad side
4 participants