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
Description:
Currently, when new requests are logged, the scroll position in the log viewer shifts, making it challenging to continue reviewing logs from a specific point. For example, if a user stops at request A to analyze logs and then switches to perform actions in the app, upon returning to the log viewer, the scroll position changes, and it’s unclear where the user left off.
Why it’s important:
Preserving the scroll position would improve the user experience by allowing seamless log analysis without losing track of where the user was.
Suggested Improvement:
It would be great to implement a feature that keeps the scroll position fixed when new logs are added, so users can continue their review without disruption.
Steps to Reproduce:
Open the log viewer and stop at a specific request (e.g., request A).
Perform actions in the app that generate new logs.
Return to the log viewer and observe the scroll position.
Current Behavior:
The scroll position shifts after new logs are added.
Desired Behavior:
The scroll position remains fixed, and the user can continue reviewing from the same point.
The text was updated successfully, but these errors were encountered:
@zhimbura thank you for your comment. I like all the details that you've included in the report. I appreciate it.
I need to think about this one. Because on iOS you never get the same instance of the Inspektify tool window and at least on that platform this wouldn't work. For other targets this could be doable, but only when an instance of the Inspektify window stays the same and does not get closed.
Description:
Currently, when new requests are logged, the scroll position in the log viewer shifts, making it challenging to continue reviewing logs from a specific point. For example, if a user stops at request A to analyze logs and then switches to perform actions in the app, upon returning to the log viewer, the scroll position changes, and it’s unclear where the user left off.
Why it’s important:
Preserving the scroll position would improve the user experience by allowing seamless log analysis without losing track of where the user was.
Suggested Improvement:
It would be great to implement a feature that keeps the scroll position fixed when new logs are added, so users can continue their review without disruption.
Steps to Reproduce:
Open the log viewer and stop at a specific request (e.g., request A).
Perform actions in the app that generate new logs.
Return to the log viewer and observe the scroll position.
Current Behavior:
The scroll position shifts after new logs are added.
Desired Behavior:
The scroll position remains fixed, and the user can continue reviewing from the same point.
The text was updated successfully, but these errors were encountered: