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
Since the design improvements introduced in this issue: #2033 some already existing cascade UI issues resurfaced. Here is one of them:
Context
The use of cascades has expanded from just using it to select administrative areas to using it for scoring. This shift in use results also in the level names not holding short one word text, as District or County, but actual questions and sentences.
The current design does not support long level names.
Problem
If the cascade level name is too long is breaks the layout in multiple places:
in the top of the cascade editor, if the level names are too long, or there are too many levels they overlap with the Add level button which is then hard to find in the screen.
In the level itself you loose the button to edit the name
This then results in the add, edit and delete clickable links for the options of the level to be out of range as well (see 2nd image)
Next steps
With this issue we do not need to introduce a large redesign of how cascades are created a that is a large endeavour, but we should aim to resolve (if possible) the above mentioned issue in the current structure
The text was updated successfully, but these errors were encountered:
@loicsans Hey Loic, I just checked the changes on glimmerofhope and if there is a long name in the level of the cascade, it looks ok on the level arrows where the name does not show fully, but there are a few issues still pending:
on the level arrows the "add level" button still overlaps (circled in the 1st image)
when editing the levels, in the level, you get that odd long scrolling to the side (see gif)
Note: the colour changes are not shown as only this branch is deployed to flowaglimmerofhope. They are, however, already merged and ready for release
Since the design improvements introduced in this issue: #2033 some already existing cascade UI issues resurfaced. Here is one of them:
Context
The use of cascades has expanded from just using it to select administrative areas to using it for scoring. This shift in use results also in the level names not holding short one word text, as District or County, but actual questions and sentences.
The current design does not support long level names.
Problem
If the cascade level name is too long is breaks the layout in multiple places:
Next steps
With this issue we do not need to introduce a large redesign of how cascades are created a that is a large endeavour, but we should aim to resolve (if possible) the above mentioned issue in the current structure
The text was updated successfully, but these errors were encountered: