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.

Sign up for GitHub

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

Jump to bottom

Strange cuisine values in the collapsible list and necessity for collapsible if there's just one value #6459

Open
Aiurek opened this issue Jan 18, 2019 · 1 comment
Open

Strange cuisine values in the collapsible list and necessity for collapsible if there's just one value #6459

Aiurek opened this issue Jan 18, 2019 · 1 comment
Labels
Nice to Have Should be fixed but there is no priority or no possibility to fix it within current horizon planning

Comments

@Aiurek
Copy link

Aiurek commented Jan 18, 2019

Lenovo Moto G4 plus, Android 7.0
OsmAnd+ 3.2.7, released 2018-11-29

If there are several attribute for the cuisine tag, it shows you messy results if u open the collapsible list:
Here, the cuisine values are "regional,swabian,italian". In the collapsible list the Regional and italian value are recognized properly, whereas there's this weird third value illustrated (where swabian is mentioned tho, among a repetition of the other values + 2 times the tag name cuisine).

Secondly, it'd be great if the collapsible list possibility would be removed if there's only one value (no matter for which tag). Otherwise, the value appears just twice if the dropdown is used.

picture10
@Aiurek
Copy link
Author

Aiurek commented Jan 18, 2019

picture14

@vshcherb vshcherb added the Nice to Have Should be fixed but there is no priority or no possibility to fix it within current horizon planning label Jan 19, 2019
@Aiurek Aiurek mentioned this issue Feb 20, 2020
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Nice to Have Should be fixed but there is no priority or no possibility to fix it within current horizon planning
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@vshcherb @Aiurek