How to set width of autocomplete popover

[doorman02]

Bug, feature request, or proposal:

Feature Request

What is the expected behavior?

The width of the autocomplete popover should be customizable

What is the current behavior?

The width is very small

What are the steps to reproduce?

Providing a Plunker (or similar) is the best way to get the team to see your issue.
Plunker template: https://goo.gl/DlHd6U

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

Content of the autocomplete can vary in size

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

Latest angular material, chrome

Is there anything else we should know?

[willshowell]

Looks like a dupe of #3198 and was fixed by #3297.

[doorman02]

Hi @willshowell will this fix be included in the next beta release? Do you know when it is planned?

[willshowell]

It should be a part of the next beta release, but I have no clue when it's planned. I'd guess early April probably?

If you want to go ahead and use all the latest changes, you can do this: (from the README)

npm install --save https://github.com/angular/material2-builds.git

[jelbourn]

Closing as duplicate of #3198

[thw0rted]

This was not exactly fixed in #3297. That disabled the (erroneous) max-width constraint, but there is still no way to control the width of the autocomplete independent from the "parent" input. The original request is that it should be "customizeable".

[willshowell]

@thw0rted see #6618 for adding a panel class

[thw0rted]

That's not actually in the release version yet, though, right? I don't know how the release cycle works; when I can expect an npm install to include this?

[willshowell]

@thw0rted no it isn't available yet - figured you may want to subscribe to it for updates. Once it's reviewed and merged, it will be available via the master-builds. Releases have typically happened ~monthly, but I think the goal is to increase the frequency.

EDIT: maybe look at #4196 (comment) for a workaround

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