Skip to content

bug(autocomplete): Autocomplete menu inside sidenav doesn't respect parent placement #20461

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

Closed
mrmokwa opened this issue Aug 31, 2020 · 4 comments
Labels
needs triage This issue needs to be triaged by the team

Comments

@mrmokwa
Copy link

mrmokwa commented Aug 31, 2020

Reproduction

sidenav_menu_bug

Expected Behavior

Autocomplete options should stick to it's parent element,
or should close the menu when scrolling.

Actual Behavior

It doesn't keep track when scrolling.

Environment

  • Angular:
  • CDK/Material: 10.1.3
  • Browser(s): Chrome 85.0.4183.83 - 64 bits
  • Operating System: Windows 10 (OS Build 19041.450)
@mrmokwa mrmokwa added the needs triage This issue needs to be triaged by the team label Aug 31, 2020
@mrmokwa mrmokwa changed the title bug(menu): Autocomplete menu inside sidenav doesn't respect parent placement bug(autocomplete): Autocomplete menu inside sidenav doesn't respect parent placement Aug 31, 2020
@mrmokwa
Copy link
Author

mrmokwa commented Aug 31, 2020

@tomicarsk6
Copy link
Contributor

Possible duplicate of #10079.

Possible solution to your problem: #10079 (comment).

@mrmokwa
Copy link
Author

mrmokwa commented Sep 1, 2020

Yeah, you're right, closing it.

@mrmokwa mrmokwa closed this as completed Sep 1, 2020
@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 Oct 2, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
needs triage This issue needs to be triaged by the team
Projects
None yet
Development

No branches or pull requests

2 participants