Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Dropdown only 1 item high on mobile #855

Closed
ghost opened this issue Jan 31, 2018 · 14 comments
Closed

Dropdown only 1 item high on mobile #855

ghost opened this issue Jan 31, 2018 · 14 comments

Comments

@ghost
Copy link

ghost commented Jan 31, 2018

@rayzorben commented on Feb 27, 2017, 5:34 PM UTC:

Make sure you are running the latest version of Home Assistant before reporting an issue.

You should only file an issue if you found a bug. Feature and enhancement requests should go in the Feature Requests section of our community forum:

Home Assistant release (hass --version): 0.39.1

Python release (python3 --version): 3.4.2

Component/platform: mobile

Description of problem: mobile UI only is 1 item high for dropdowns such as the source in media player. Very difficult to select an item.

Expected: UI would allow at least 3-4 items to easily find the correct one.

Problem-relevant configuration.yaml entries and steps to reproduce:
screenshot

Traceback (if applicable): N/A

Additional info:

This issue was moved by @MartinHjelmare from home-assistant/core/issues/6285.

@ghost
Copy link
Author

ghost commented Jan 31, 2018

@cyberjunky commented on Feb 27, 2017, 6:52 PM UTC:

Look here for older thread about this...
https://community.home-assistant.io/t/more-user-friendly-combobox-on-mobile-devices/6820

@ghost
Copy link
Author

ghost commented Jan 31, 2018

@rayzorben commented on Feb 27, 2017, 9:11 PM UTC:

Seems like a bug to me though.

@ghost
Copy link
Author

ghost commented Jan 31, 2018

@balloobbot commented on Apr 30, 2017, 6:37 AM UTC:

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.

Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍

@ghost
Copy link
Author

ghost commented Jan 31, 2018

@bieniu commented on Apr 30, 2017, 9:33 AM UTC:

Fixed.

@ghost
Copy link
Author

ghost commented Jan 31, 2018

@schotime commented on May 5, 2017, 1:17 PM UTC:

I'm still getting this in 0.43.2 on chrome on android.

@ghost
Copy link
Author

ghost commented Jan 31, 2018

@schotime commented on Jul 4, 2017, 9:40 AM UTC:

This is still really annoying on 0.48. @balloob

20170704_193851

@ghost
Copy link
Author

ghost commented Jan 31, 2018

@balloob commented on Jul 5, 2017, 4:36 AM UTC:

Don't tag names of developers please. It doesn't help.

@ghost
Copy link
Author

ghost commented Jan 31, 2018

@balloobbot commented on Sep 4, 2017, 11:36 PM UTC:

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.

Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍

@ghost
Copy link
Author

ghost commented Jan 31, 2018

@schotime commented on Sep 5, 2017, 12:06 AM UTC:

This still exists in 0.52.1.
Thanks.

@ghost
Copy link
Author

ghost commented Jan 31, 2018

@bboti86 commented on Sep 24, 2017, 9:25 AM UTC:

This still exists on the 0.54 version as well.

@ghost
Copy link
Author

ghost commented Jan 31, 2018

@deluxestyle commented on Nov 19, 2017, 5:22 PM UTC:

still exists in 0.58

@ghost
Copy link
Author

ghost commented Jan 31, 2018

@cgarwood commented on Jan 11, 2018, 8:28 PM UTC:

This appears to be a polymer bug on iOS, so there's not a whole lot we can do at the moment. There's a similar active issue at home-assistant/home-assistant-polymer#775

@ghost
Copy link
Author

ghost commented Jan 31, 2018

@ciotlosm commented on Jan 31, 2018, 9:38 PM UTC:

@MartinHjelmare can this issue be moved to home-assistant-polymer repo?

@NovapaX
Copy link
Contributor

NovapaX commented Mar 9, 2018

This should be closed with #775 by #854
If not, a new issue should be opened imo

@balloob balloob closed this as completed Mar 9, 2018
@github-actions github-actions bot locked and limited conversation to collaborators Jul 7, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants