Open phiphi-tan opened 10 months ago
It is natural for multiple scrollbars to appear for multiple containers. Multiple containers can't share the same scrollbar, that would be way more disruptive.
Team chose [response.Rejected
]
Reason for disagreement: >It is natural for multiple scrollbars to appear for multiple containers.
This is a clear feature flaw that the dev team decided to continue adopting, with the assumption that "it is natural". It is indisputable that the existence of multiple scrollbars is cumbersome and does not contribute to an overall good UX design
Multiple containers can't share the same scrollbar, that would be way more disruptive.
While the above may be true, the team is ignoring the fact that multiple scrollbars in and of itself are already disruptive to the users.
Fix:
Given their JavaFX based UI, they could have used a TextFlow
container to contain these remarks, which would have dynamically wrapped the text and prevented the use of many scrollbars.
They could also have changed the text wrapping on their items in order to prevent the scrollbar issue. This would prevent the issue of too many scrollbars from occuring while still maintaining the apps functionality, and preventing the user from being overwhelmed by the scrollbars
This issue exists to users as it is disruptive to their workflow and should not be rejected simply because the team assumed that multiple scrollbars were the best possible representation.
If there are multiple long remarks, many scrollbars will appear for the user, which is slightly annoying for the user to deal with