If md-slider changes position after initialization, it can't be clicked in the new location

[alxhub]

Bug, feature request, or proposal:

Bug

What is the expected behavior?

If md-slider changes position on the page after initialization (e.g. if an NgIf becomes true and more elements appear), it should be usable in the new position.

What is the current behavior?

If md-slider changes position on the page after initialization , clicking the slider bar will not work. Clicking the handle results in the handle being rendered far to the right of the mouse pointer.

What are the steps to reproduce?

In plunker: http://plnkr.co/edit/dAKSvx6Evjpz1Z5D2DQ7?p=preview

Load the plunk, wait for the hidden content to be shown after 1s timer. Then, try to use the slider.

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

It's horribly broken!

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

Unknown, but would guess plunker is using the latest.

Is there anything else we should know?

Feel free to ask me to show you the issue in my real app. :)

[crisbeto]

There was a change, at some point, that made the slider get the dimensions on mouse enter, instead of on init. Might be worth updating since it looks like the Material version in the Plunker template is old.

[DSchrupert]

Looks like @crisbeto is correct. After updating the systemjs.config.js to:
'@angular/material': 'https://unpkg.com/@angular/[email protected]',
resolves this issue when i tried.

[jelbourn]

@mmalerba can you investigate?

[mmalerba]

yeah, this was fixed by #1663

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