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
Describe the bug
Using the Share URL, a user can grab the URL to a specific section in a multi-section item. When loading that URL, the media object loads and the correction Canvas is highlighted in the structure, but the structure does not auto-scroll so the current Canvas is visible.
Currently, tested only in Chrome in on avalon-staging.
The highlighted section, Free_Test_Data_1OMB_MP3, appears.
Scroll back up to the top of the section list.
Begin playback
The structure still does not jump to the current section even after playback starts.
Expected behavior
When a start canvas is specified, the structure should auto-scroll so the specific canvas is visible. Anytime a canvas begins playback, the structure should auto-scroll so that canvas is visible.
Screenshots
Screen.Recording.2024-11-25.at.1.31.47.PM.mov
Desktop (please complete the following information):
OS: MacOS Sequoia
Browser Chrome
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered:
Describe the bug
Using the Share URL, a user can grab the URL to a specific section in a multi-section item. When loading that URL, the media object loads and the correction Canvas is highlighted in the structure, but the structure does not auto-scroll so the current Canvas is visible.
Currently, tested only in Chrome in on avalon-staging.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
When a start canvas is specified, the structure should auto-scroll so the specific canvas is visible. Anytime a canvas begins playback, the structure should auto-scroll so that canvas is visible.
Screenshots
Screen.Recording.2024-11-25.at.1.31.47.PM.mov
Desktop (please complete the following information):
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: