Skip to content

Conversation

@tyrasd
Copy link
Member

@tyrasd tyrasd commented Jul 29, 2025

Resolves #9677.

Affected are fields of the type:

  • number
  • roadHeight
  • roadSpeed
  • (implicitly also the layer subfield of the structure field)
  • date

Not included are addr:housenumber, addr:postcode which can be numeric, but are often of a mixed nature.

Example (just for fun in a locale with a localized decimal separator):

image

I'm not quite 100% convinced that this is really a benefit overall:

  • ➕ It brings the numeric value closer to the unit/measurement or the + / - buttons
  • ➖ It's a little harder to see if a field is empty when quickly scanning from top to bottom
  • the biggest benefit of right-aligning numbers is when numbers are represented in tabular form (e.g. on a spreadsheet), where it affords one to quickly compare numeric values by their length and their most significant digit. This is not really the case for numeric fields in iD.

What do you think? //cc @1ec5

@tyrasd tyrasd added the field An issue with a field in the user interface label Jul 29, 2025
@tyrasd tyrasd marked this pull request as draft July 29, 2025 11:33
@tordans
Copy link
Collaborator

tordans commented Jul 29, 2025

I don’t think this is an improvement. It puts the data where the UI is very dense making it harder to see. And makes the data harder to scan.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

field An issue with a field in the user interface

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Right-align numeric fields

3 participants