ConnectedOverlayDirective.positions is not assignable?

[jessedhillon]

Bug, feature request, or proposal:

See this commit jessedhillon@eedd965

The positions attribute on a connected-overlay element is ignored.

What is the expected behavior?

When the positions attribute is set on an element with [connected-overlay] the component should use those ConnectedPositionPair instances.

What is the current behavior?

The default positions are always used.

What are the steps to reproduce?

Check out my bug-overlay-directive-positions branch. I've added one new spec and fixture to demonstrate the issue.

I couldn't get your plunkr template to demonstrate the issue, or load the overlay directive, because the angular version is too low. I was just recreating the test component from my branch anyhow.

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

Users of connected-overlay would want to align the overlay to the trigger

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

angular-2.0.0-alpha-7.2

Is there anything else we should know?

I dug down into the JS internals a bit and the propMetadata map returned when reflecting on ConnectedOverlayDirective only has the origin key in it, it should have a positions key as well.

[jessedhillon]

I think something else was the issue here, disregard.

[angular-automatic-lock-bot]

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.}