We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
bug
the menu should be completely visible
the menu position is wrong, the menu is not completely visible
the bug only appears on mobile devices
<style type="text/css"> .my-button { display: inline-block; position: fixed; bottom: 20px; right: 20px; z-index: 2; } </style> <md-menu #createMenu="mdMenu" y-position="above" x-position="before"> <button *ngFor="let a of [1,2,3]" md-menu-item> {{ 'Button ' + a }} </button> </md-menu> <button class="my-button" md-fab [mdMenuTriggerFor]="createMenu" color="primary">+</button>
the user wants to see the full menu
angular 4.3.2, angular material 2.0.0-beta.8, typescript 2.4.2, mobile safari, mobile chrome
The text was updated successfully, but these errors were encountered:
Closing as this is tracking in #6534
Sorry, something went wrong.
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.
No branches or pull requests
Bug, feature request, or proposal:
bug
What is the expected behavior?
the menu should be completely visible
What is the current behavior?
the menu position is wrong, the menu is not completely visible
What are the steps to reproduce?
the bug only appears on mobile devices
What is the use-case or motivation for changing an existing behavior?
the user wants to see the full menu
Which versions of Angular, Material, OS, TypeScript, browsers are affected?
angular 4.3.2, angular material 2.0.0-beta.8, typescript 2.4.2, mobile safari, mobile chrome
Is there anything else we should know?
The text was updated successfully, but these errors were encountered: