isUserInput == false when cycling through closed select

[willshowell]

Bug, feature request, or proposal:

Bug

Expected behavior

When cycling through options in a closed select with the up and down keys, I'd expect the MdOptionSelectionChange to have isUserInput == true

Current behavior

isUserInput is only true when selected from an open select.

Reproduction

http://plnkr.co/edit/YQn77sSXj60cNwLYldOC?p=preview

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

I want to trigger an event when the user

1. Opens the select and changes the value with mouse or keyboard
2. Opens the select and reselects the current value mouse or keyboard
3. Cycles to a new option while the select is closed

It's easy to achieve 1 and 3 with the the select's (change) event. In order to get 2, I have to instead watch each option's (onSelectionChange) event and filter by event.source.selected. At this point, I cannot tell the difference between changes made by the ControlValueAccessor interface or by the user cycling through the closed select.

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

Latest (c2816ef)

Is there anything else we should know?

I may be misinterpreting the use of isUserInput but it would seem that cycling through a closed select would be considered "selection coming from the user".

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