You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Text input fields in the text editor should allow text to be edited with ease, regardless of how much content they contain
Solution ideas
Fixed ratio of key to value field of 50% each (minus necessary padding and ℹ️ button space) for a uniform look. Probably not the best idea as there are tags where the key is regularly way shorter than the value. But could be worth toying with.
Max width (ratio), e.g. 70% for key and/or value field
Allow key and value input fields to have multiple lines
Should probably be soft-wrap and newlines disallowed for most cases?
Examples of the issue
Annoying
Fields like opening_hours can easily become quite lengthy and it’s more cumbersome to scroll through them or see at a glance if all special rules for a place are already taken care of.
Impossible
If tag keys become so lengthy that they fill the whole width, you cannot even see the value field. It’s possible to tap on the key and press the “Next” button above the keyboard, but then I still cannot see the content of the value field.
Feature request
Text input fields in the text editor should allow text to be edited with ease, regardless of how much content they contain
Solution ideas
Examples of the issue
Annoying
Fields like
opening_hours
can easily become quite lengthy and it’s more cumbersome to scroll through them or see at a glance if all special rules for a place are already taken care of.Impossible
If tag keys become so lengthy that they fill the whole width, you cannot even see the value field. It’s possible to tap on the key and press the “Next” button above the keyboard, but then I still cannot see the content of the value field.
Super long key tag as an example:
seamark:shoreline_construction:water_level
for https://www.openstreetmap.org/way/854244002The text was updated successfully, but these errors were encountered: