Page MenuHome

User Interface Policies
Confirmed, NormalPublicDESIGN


Design task to coordinate user interface policies before including them in the human interface guide-lines (HIG).

This is a curated list of items agreed on by module owners.

Order of importance:

  • Very Important - These we should handle before the next release.
  • Somewhat Important - These issues would be nice to do as soon as possible.
  • Less Important - Extra polish, nice to have.
  • ? Incomplete - Tasks needing more details before implementing.

Under Discussion


  • <none>


Event Timeline

Julian Eisel (Severin) changed the subtype of this task from "Report" to "Design".May 18 2020, 4:58 PM

For inclusion of "Rejected: UI: Comma as Decimal Separator" it would be nice to see more detailed policy related to this sort of thing.

That particular patch allowed users to select the usage of comma for decimal separator and, when doing so, then used decimal for large integer grouping. So are we saying that we are against all locale-specific customization or just things that impact numbers? Are we officially just tied to USA patterns?

We could move towards a more international stance. So for things like large integer grouping we could use thinspace instead of comma, which has been the current international recommendation for a while.

Similarly we could ALLOW the use of comma when entering numbers, but just treat it as if the user hit decimal. Everything would still display as it does today, but it would be a convenience for users who have OS settings or hardware that favors comma for decimal. For example, note that comma is output in the numerical keypad on this keyboard:

Philipp Oeser (lichtwerk) changed the status of subtask T76227: Make All Operators Accessible from Menus from Needs Triage to Confirmed.Oct 20 2020, 12:07 PM