Uploaded image for project: 'Magnolia UI'
  1. Magnolia UI
  2. MGNLUI-2347

White-space characters are almost invisible, when used as values in trees and lists

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Open
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: 5.1, 5.3, 5.4.1
    • Fix Version/s: 5.3.x, 5.4.x
    • Component/s: tree/list
    • Labels:

      Description

      If you're using whitespace characters in values shown in a tree or list, t*hose whitespace characters are almost invisible due to the proportional font we're using*. Furthermore, whitespace characters at the front and at the end of a string are removed for display as we trim all strings showing up as values.

      This is quite a usability issue as it makes it hard to find accidentally entered whitespace characters, e.g. in the configuration tree. You essentially have to double-click on a value to enter edit mode to be able to detect it at all.

      I've attached an example, where I deliberately enter leading spaces in front of a number. This leads to an exception, as this doesn't result in a valid number, but it doesn't show in the tree, as the leading space characters are stripped away before being shown. They are still there, though.

      I suggest we do the following:

      • We make it optional to trim strings in certain trees (e.g. config) or simply no longer trim strings at all. After all, the whitespace characters are part of the value as it was entered.
      • We show the full value using a tooltip: we show the Unicode "open box" character instead of space characters everywhere and use a monospace font there to make it easier to discern whitespace from regular characters.

        Attachments

          Activity

            People

            Assignee:
            Unassigned Unassigned
            Reporter:
            weder Andreas Weder
            Votes:
            1 Vote for this issue
            Watchers:
            2 Start watching this issue

              Dates

              Created:
              Updated:
              Date of First Response: