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
I have searched the existing issues for this feature request and I know that duplicates will be closed
Is your feature request related to a problem?
When selecting a group or request within a collection in the collection sidebar, the scroll position of that list updates to place the selected request at the top of the viewing area. This behavior doesn't appear to happen when selecting a collection in the list. I propose this abrupt jump when selecting a request is a generally undesirable UX behavior, even if only subconsciously/subliminally. When the selection jumps, it makes me feel like what I was working with has disappeared out from under me; it makes me feel like the surface I'm working on is unstable, and, as silly as it might sound, I feel slightly anxious about it. It also undermines the hierarchical presentation of collections/groups/requests in the UI by continually hiding visual context of what group a request belongs to and what other siblings precede it in the list.
Describe the solution you'd like
I'm requesting this jumping scroll behavior be removed from the UI or at least made optional via configuration.
Describe alternatives you've considered
If disabling or removing this behavior is off the table, a more attractive alternative might be to smoothly scroll to the new position instead of immediately jumping. That would compromise between restoring some visual continuity and visual context, on one hand, and the presumptive goal of the behavior of resetting/orienting "you are here", on the other hand.
Along with that, either setting or configuring a different "home" scroll position instead of the top (e.g. 33% from the top for "rule of thirds", 38% for "golden ratio", or 50% for "right in the middle") would go further to maintain surrounding visual context--i.e., to be able to continue to see the request's group and/or preceding siblings.
Additional context
No response
The text was updated successfully, but these errors were encountered:
Is there an existing request for this feature?
Is your feature request related to a problem?
When selecting a group or request within a collection in the collection sidebar, the scroll position of that list updates to place the selected request at the top of the viewing area. This behavior doesn't appear to happen when selecting a collection in the list. I propose this abrupt jump when selecting a request is a generally undesirable UX behavior, even if only subconsciously/subliminally. When the selection jumps, it makes me feel like what I was working with has disappeared out from under me; it makes me feel like the surface I'm working on is unstable, and, as silly as it might sound, I feel slightly anxious about it. It also undermines the hierarchical presentation of collections/groups/requests in the UI by continually hiding visual context of what group a request belongs to and what other siblings precede it in the list.
Describe the solution you'd like
I'm requesting this jumping scroll behavior be removed from the UI or at least made optional via configuration.
Describe alternatives you've considered
If disabling or removing this behavior is off the table, a more attractive alternative might be to smoothly scroll to the new position instead of immediately jumping. That would compromise between restoring some visual continuity and visual context, on one hand, and the presumptive goal of the behavior of resetting/orienting "you are here", on the other hand.
Along with that, either setting or configuring a different "home" scroll position instead of the top (e.g. 33% from the top for "rule of thirds", 38% for "golden ratio", or 50% for "right in the middle") would go further to maintain surrounding visual context--i.e., to be able to continue to see the request's group and/or preceding siblings.
Additional context
No response
The text was updated successfully, but these errors were encountered: