When users create cascades they define the level names and then the options. There is no character limit imposed. We have cases where cascades are used for scoring. In these cascade the options can hold long descriptions the users needs to comply with. So we moved away from short one words, to long sentences
Problem
When the user defines a long cascade option name, it does not fit in the UI and overlays with the edit and delete links
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Since the design improvements introduced in this issue: https://github.com/akvo/akvo-flow/issues/2033 some already existing cascade UI issues resurfaced. Here is one of them:
Context
When users create cascades they define the level names and then the options. There is no character limit imposed. We have cases where cascades are used for scoring. In these cascade the options can hold long descriptions the users needs to comply with. So we moved away from short one words, to long sentences
Problem
When the user defines a long cascade option name, it does not fit in the UI and overlays with the edit and delete links