Specific position for MdMenu

[NCC1701M]

Bug, feature request, or proposal:

Feature

What is the expected behavior?

It might be useful to set explicitly the position of the MdMenu by using real x and y coordinates.

What is the current behavior?

When you open the menu programmatically via the ViewChild you can only set for position "above" and "below" respectively "before" and "after"

What is the use-case or motivation for changing an existing behavior?

I have a svg with several paths. When I click on one of these paths I'd like to show a Menu with actions. I have to call it programmatically. I assigned the mdMenuTriggerFor on a hidden input field. But now the menu will always be displayed on the top left corner.

Which versions of Angular, Material, OS, browsers are affected?

Material: 2.0.0-beta.1
OS: Microsoft Windows [Version 6.1.7601]
Browser: Chrome Version 55.0.2883.87 m

[arlowhite]

I would like this option too. There are many cases where you would want to show a menu at different locations in response to a click event.

• Right-click table cell or column to show a menu.
• Right-click chart to show options.

This feature also means that you should be able to create a MdMenu without an associated MdMenuTrigger. Or, at least you should be able to create a MdMenu without a trigger and specify a single-use trigger via the API:

this.menu.openAtElement(event.target)

[instantaphex]

@arlowhite I've come up with a work-around for the time being that works fairly well. I've added an ngStyle to an invisible, absolutley positioned trigger that updates the top and left based on mouse click.

[angular-robot]

Just a heads up that we kicked off a community voting process for your feature request. There are 20 days until the voting process ends.

Find more details about Angular's feature request process in our documentation.

[NCC1701M]

Wow, only 5 years after the issue was created 👍🏻

[angular-robot]

Thank you for submitting your feature request! Looks like during the polling process it didn't collect a sufficient number of votes to move to the next stage.

We want to keep Angular rich and ergonomic and at the same time be mindful about its scope and learning journey. If you think your request could live outside Angular's scope, we'd encourage you to collaborate with the community on publishing it as an open source package.

You can find more details about the feature request process in our documentation.

[crisbeto]

This sounds like a duplicate of #5007. Also it's worth noting that the CDK menu has this already and the Material menu should get it for free once it's switched over to use it.