Why does this script break the timestamp seeking functionality?
|
|
First of all, I've been using YousableTubeFix for about 4 or 5 months now, and I love it. It's one of my favorite things about Firefox. Now, a couple of months ago, YouTube introduced the ability to click a timestamp noted in comments (e.g. 1:57) and have the video immediately skip to that point. I've noticed that on when using a browser with YousableTube, it seems as though this function rarely works, if at all. Is this a known issue? Has anyone else noted this happening? Or do I just have bad luck? |
|
|
I've had the same issue.
|
|
|
Yeah. That needs some investigation, I guess. |
|
|
Glad I'm not alone, then. I see that in your post you mentioned disable-autoplay, but I don't even use that option and I still am affected by this bug. Then again, seeking seems to work for me at least half of the time, so I really don't know what it is. |
|
|
Normal seeking (using the player timeline) works for me in FLV but sometimes it doesn't work in MP4 format, with or without the script enabled, so that's not a problem of the script. Timestamp seeking often breaks when the script is enabled. According to the error console, it's because the YouTube code sends the command to the player, but the player doesn't expose the used function (seekTo, a YouTube API function). I don't know why that happens, as the player is a Flash application, so I can't debug it. I can try to decompile the player, understand the code and try to find the error, but as you should understand, that's a very difficult task. If anyone has an idea of why this is happening, please tell me. |
|
|
maybe check http://code.google.com/apis/youtube/js_api_refe... ? Another feature to add would be to disable non-flv media if there's an indicated seek in the url (ie #t) |
|
|
The problem with URL seeking can happen too with FLV formats, so that won't help :-( . Normal seeking always works with FLV though. |
![]() ![]() |
Any luck on fixing this problem? |

