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
mat-menu should be sticked to the place whare it was triggered
menu jumps when scrollin or moves in oposite direction
I think no comments are required here
Angular CLI: 6.0.3 Node: 8.11.1 OS: win32 x64 Angular: 6.0.2 ... animations, common, compiler, compiler-cli, core, forms ... http, language-service, platform-browser ... platform-browser-dynamic, router, service-worker
@angular-devkit/architect 0.6.1 @angular-devkit/build-angular 0.6.1 @angular-devkit/build-optimizer 0.6.1 @angular-devkit/core 0.6.1 @angular-devkit/schematics 0.6.3 @angular/cdk 6.1.0 @angular/cli 6.0.3 @angular/flex-layout 6.0.0-beta.15 @angular/material 6.1.0 @angular/pwa 0.6.3 @ngtools/webpack 6.0.1 @schematics/angular 0.6.3 @schematics/update 0.6.3 rxjs 6.1.0 typescript 2.7.2 webpack 4.6.0
You can reproduce it using google chrome developer tools just by toggling device toolbar (Ctrl + Shift + M on windows)
The text was updated successfully, but these errors were encountered:
Closing as a duplicate of #11365.
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?
mat-menu should be sticked to the place whare it was triggered
What is the current behavior?
menu jumps when scrollin or moves in oposite direction
What are the steps to reproduce?
What is the use-case or motivation for changing an existing behavior?
I think no comments are required here
Which versions of Angular, Material, OS, TypeScript, browsers are affected?
Angular CLI: 6.0.3
Node: 8.11.1
OS: win32 x64
Angular: 6.0.2
... animations, common, compiler, compiler-cli, core, forms
... http, language-service, platform-browser
... platform-browser-dynamic, router, service-worker
Package Version
@angular-devkit/architect 0.6.1
@angular-devkit/build-angular 0.6.1
@angular-devkit/build-optimizer 0.6.1
@angular-devkit/core 0.6.1
@angular-devkit/schematics 0.6.3
@angular/cdk 6.1.0
@angular/cli 6.0.3
@angular/flex-layout 6.0.0-beta.15
@angular/material 6.1.0
@angular/pwa 0.6.3
@ngtools/webpack 6.0.1
@schematics/angular 0.6.3
@schematics/update 0.6.3
rxjs 6.1.0
typescript 2.7.2
webpack 4.6.0
Is there anything else we should know?
You can reproduce it using google chrome developer tools just by toggling device toolbar (Ctrl + Shift + M on windows)

The text was updated successfully, but these errors were encountered: