Timeline - Improve recording/position changes with keyboard controls #275
Replies: 9 comments 7 replies
-
|
Commit pushed to main for this. |
Beta Was this translation helpful? Give feedback.
-
|
This is working great in 3bf4298. I noticed two things that could be improved.
|
Beta Was this translation helpful? Give feedback.
-
|
Tested in b5ed773. This is working amazing! All of it. One more change and I think this is golden. When in 'fine' mode, could the arrow keys advance/rewind the video by the selected |
Beta Was this translation helpful? Give feedback.
-
|
Tested in 3345132. The change works well. Can you make it so clicking the speed buttons does not take the user out of 'fine' mode. That would avoid having to re-click the video to continue at the new speed. In my excitement, I prematurely said this was done. I found some intermittent instabilities in later testing yesterday that I am trying to figure out how to reliably reproduce:
|
Beta Was this translation helpful? Give feedback.
-
|
Tested in c1a912f. When the timeline has focus and a key press occurs, a black box appears around it. That should not happen. When the timeline is clicked and the focus remains on the timeline, a single tap of an arrow key will jump in the expected direction by what appears to be 33 minutes. As long as the video is allowed to complete its loading cycle, this can be repeated infinitely in either direction. If the video is not allowed to complete its loading cycle, the behavior seems random and uncontrollable. Having the timeline focused should not affect keyboard navigation. The When the video control is focused, tapping the space bar results in a double play/pause toggle, cancelling each out. There is still instability in 'fine' mode when sequentially viewing recordings in a forward direction.
The play/pause repeating loop issue still happens (but maybe not as often?). I have not been able to reliably reproduce it but I've seen it occasionally happen while putting together the reproduction steps for the previous issue above (Auto switching to play when loading the next recording and there is an immediate gap in the timeline). I cannot rule out the length of the recording (i.e. not being a full segment length) or the length of the gap between recordings as contributing factors. Otherwise, I think progress is great! |
Beta Was this translation helpful? Give feedback.
-
|
Tested with commit c39a590. The ability to switch keyboard navigation modes should be disabled when the Delete and Recording Tag modals are shown. Otherwise, this is much improved. I will keep testing. |
Beta Was this translation helpful? Give feedback.
-
|
Working great in 9f90854. I will keep testing. |
Beta Was this translation helpful? Give feedback.
-
|
Testing in commit 767ed94. The issue with the seemingly un-endable fast play/pause loop is back. It occurs intermittently. It occurs more often in Firefox than in Chrome. Usually to trigger this all I have to do is load the timeline, hit spacebar to immediately start playing, then hit space bar again to stop (and enter the loop). Sometimes, if that doesn't work, I can get it to happen after seeking around a bit with the arrow keys and/or clicking the timeline. |
Beta Was this translation helpful? Give feedback.
-
|
Tested in commit b624c98. Have not seen the fast play/pause loop again, but have not tested as much due to issues with the timeline. I will keep monitoring this. New issue...
|
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
This is based off of d8a219d.
In that commit, there is the following:
All of these actions are mostly mouse or touch oriented.
I had been thinking for a while once an interesting section of the timeline has been identified (using the new pan and zoom controls), that it would be great if the user could use the arrow keys on their keyboard to sequentially scan between recordings at a broad level and within a recording at a fine level, while keeping the overall interactions with the page to a minimum.
The changes below are a very initial and rough attempt to address this goal.
With these changes:
Let me know what you think, please.
Beta Was this translation helpful? Give feedback.
All reactions