-
-
Notifications
You must be signed in to change notification settings - Fork 3.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Change timestamp behavior #4241
Comments
why bug @opusforlife2 @TobiGr? |
Unexpected behaviour compared to Youtube and Invidious? |
That's how I differentiate between the two, anyway. Bug: did something and got an unexpected result. |
It is expected here. We did not change code about this therefore we do not expect the behavior to change. |
You're speaking from the perspective of a developer here. There is probably no bug in the code, sure. But from a user's perspective, there is a bug in the behaviour. No user would tap on a timestamp and expect to see a popup of the same video. And it's not documented anywhere in the app that that's something that will happen. Any user who's used this functionality in Youtube or Invidious will expect to jump to that timestamp in the same video, though. |
It's definitely not a bug with the unified player, but existing behaviour from the past, so that should be removed from the title, I agree. |
Ah yes. I think avently was testing this out at some point, but it wasn't implemented. I forgot why.
Would it not be possible to have the app 'jump' to the top upon tapping a timestamp? I don't see why someone would tap several timestamps in a row, anyway. That seems like a corner case. |
Also, how does this possibility sound? : If the video is paused, then it should scroll up just like it currently does, letting comments or suggested videos fill up the screen. But if the video is playing, then comments and videos should scroll under it. |
I didn't see this as unintended behavior, that's why I posted this as a feature request. I felt this suggestion was more relevant and doable now that the player is going to work more like YouTube's. I honestly don't see the reason why timestamps have to make additional instances of the player if we already have a system that works in-line with the user interface. My suggestion for the comments issue would be to compress the player about half it's height to the upper edge to make more room for the comments. |
@opusforlife2 let's see from a developer perspective. For you it may may sounds the same but because you don't write a code. It's like saying "a bug" when I disagree with your point in a comment:) |
Fair enough. |
Hi, i think that you can create an option in settings where the user can choose two differents method:
In this way the user can choose the best option for him. What do you think about that? |
How about this:
? |
That makes a lot of sense, sryze. Seems to offer the best of both worlds. |
Keeping the video static while scrolling comments is a major feature and it'll be added anyway. #4484 should be considered in this regard to make the feature useful on main player.
Long tap gesture should be preserved for copying links in comments and description as suggested in #7097 and #7378. Popup player will be required no more if my first suggestion is implemented, I think. |
link? |
@yashpalgoyal1304 #4484 |
i dont think that that'd be a good idea
|
... cntd.
|
This behavior got super weird lately. When you tap on a timespan it opens a popup player not from the timestamp but from the position you were watching. Then you can tap the timestamp again to make the popup player jump to that position. Then you can close the popup player and main player resumes from where popup player left. Doesn't resemble an intended behavior. |
@SomeoneIsWorking This issue is expected to continue playing timestamp on current player. Please have a look at #7427 instead. |
same thing happens to me as well, except it takes around 8 seconds for the video to continue playing in popup mode and another 8 to go back to its original place I think the video should jump to the intended timestamp when you press it, same way how it works across all other apps and frontends |
So, one way - building on the one
one way to further improve further improve the experience using popup mode itself:
|
How about just letting users globally configure the player to be used for timestamp clicks? Would at least be useful for audio-only whole-album videos where timestamps seek to different songs. In this case users don't care about the video. I tried changing The best solution seems to be figuring out the sticky video at the top if user wants it. Unlike the popup it would not obstruct content at the top of the page. |
You are right. #4484 should be implemented before this issue. There's no need to make timestamp behavior customizable. Rather, continuous playback on current player is fine. |
This comment was marked as spam.
This comment was marked as spam.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
@adamency In both issues, a toggle would be the ultimate solution as you said. Unfortunately, I doubt the reason we're not getting these features is that the developers are undecided. It's just that they're trying to keep up with the changes made to Youtube on the regular + fixing up bugs + rewriting the entire codebase. I'm not sure if they're going to make any improvements to the current app considering the last point. |
Maybe there should be two teams : one focused on scraping, the other focused on the rest. |
Describe the feature you want
Timestamps should seek in the Unified Player instead of starting a pop-out player.
Is your feature request related to a problem? Please describe it
N/A
Additional context
N/A
How will you/everyone benefit from this feature?
Timestamp-based pop-out players are the inferior solution compared to instantly seeking in the unified player.
The text was updated successfully, but these errors were encountered: