Open woojiahao opened 12 months ago
Thank you for pointing this out, however, this issue is easily solved by expanding the window.
Team chose [response.Rejected
]
Reason for disagreement: This is my response to the issue of a missing scrollbar:
This should not be rejected as it is a completely valid bug with the UI. There may be a chance that the user has display limitations making it impossible for them to scale the window to tag section label. The Rejected status should be reserved for when missing the tag section label is expected and correct behavior but by no means is having a missing UI components supposed to be expected, especially in the constraint mentioned above. Just because there's a possible fix that can be applied, does not mean that it is a universal fix (which it isn't in this case) and more can, and should, definitely be done to accommodate for this issue as well. This does not mean that it needs to have been done within the period of the TP, but certainly something that can be done as a future iteration.
In fact, a screen size limitation is a completely valid concern as another report I had raised where the team had considered "CannotReproduce" because their screen could not scale any larger. The team has faced, first hand, how a limited screen real estate can make it hard to replicate and respond to bug reports, hence, I don't see how "just resizing" and Rejecting is a valid response to a UI bug.
May make it hard to discern what that field should be