[MGNLUI-2347] White-space characters are almost invisible, when used as values in trees and lists Created: 04/Nov/13 Updated: 09/Mar/21 Resolved: 09/Mar/21 |
|
| Status: | Closed |
| Project: | Magnolia UI |
| Component/s: | tree/list |
| Affects Version/s: | 5.1, 5.3, 5.4.1 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major |
| Reporter: | Andreas Weder | Assignee: | Unassigned |
| Resolution: | Obsolete | Votes: | 1 |
| Labels: | next, usability, ux | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
| Template: |
|
| Acceptance criteria: |
Empty
|
| Task DoD: |
[ ]*
Doc/release notes changes? Comment present?
[ ]*
Downstream builds green?
[ ]*
Solution information and context easily available?
[ ]*
Tests
[ ]*
FixVersion filled and not yet released
[ ] 
Architecture Decision Record (ADR)
|
| Bug DoR: |
[ ]*
Steps to reproduce, expected, and actual results filled
[ ]*
Affected version filled
|
| Date of First Response: |
| 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:
|
| Comments |
| Comment by Simon Aebli [ 02/Dec/14 ] |
|
I just had this problem in the config tree in Magnolia 5.3. |