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
Thumbnail strip in imagery view is organized chronologically, ascending left to right, with most recent image telemetry on the right. If, paused, on resume, the paused image (and other older images) can get stuck to the right side of the thumbnail strip, if the strip was paused for too long. My guess is too long refers to when the images were to scroll off screen.
Upon further investigation, the root cause is images are not being removed if multiple images are to be removed in the same event. Pausing was the only way I could reliably reproduce this (although I'm not 100% sure why that plays a role).
VIPERGC-577
Expected vs Current Behavior
Expect on resume, all thumbnails are present and in order, and focus goes to the most recent, right most, image.
Steps to Reproduce
Navigate to an example imagery object, with the time conductor in realtime mode
Pause telemetry by clicking on an image, or clicking the pause button located above the thumbnail strip
Wait for a while... (My guess is until when the images were to scroll off screen)
Resume telemetry
Observe that when new telemetry comes in, the paused images are stuck to the right of the incoming telemetry (timestamp and staleness indicator will indicate)
Environment
Open MCT Version:
Deployment Type:
OS:
Browser:
Impact Check List
Data loss or misrepresented data?
Regression? Did this used to work or has it always been broken?
Is there a workaround available? Refresh or change time conductor bounds to force a reload
Does this impact a critical component?
Is this just a visual bug with no functional impact?
Does this block the execution of e2e tests?
Does this have an impact on Performance?
Additional Information
The text was updated successfully, but these errors were encountered:
davetsay
changed the title
[Imagery] Pausing in realtime mode for too long prevents proper resume functionality
[Imagery] Some images not being bounded properly
Sep 20, 2024
* more readable
* unpause explicitly
* fix jsdoc
* e2e testing multiple image removal
* prettier
* fix to remove multiple images from history
* move tests that use playwright clock api into own file
* fix playwright clock tests
* add aria-label to element
* prevent straggler debounced function call on unmount
* clean up and fix tests
* update paths
* lint fix
* lint fix
---------
Co-authored-by: John Hill <[email protected]>
Summary
Thumbnail strip in imagery view is organized chronologically, ascending left to right, with most recent image telemetry on the right. If, paused, on resume, the paused image (and other older images) can get stuck to the right side of the thumbnail strip, if the strip was paused for too long. My guess is too long refers to when the images were to scroll off screen.
Upon further investigation, the root cause is images are not being removed if multiple images are to be removed in the same event. Pausing was the only way I could reliably reproduce this (although I'm not 100% sure why that plays a role).
VIPERGC-577
Expected vs Current Behavior
Expect on resume, all thumbnails are present and in order, and focus goes to the most recent, right most, image.
Steps to Reproduce
Environment
Impact Check List
Additional Information
The text was updated successfully, but these errors were encountered: