Safari bug February 12, 2011 7:36 AM Subscribe
Safari 'in-page' player youtube glitch.
When I click on the 'play' button on a youtube video it works fine the first time. The second time (and subsequent times) I click on the 'play' button it shows me the first video I saw. This is just for the metafilter 'in-page player. If I click through to the video everything is fine.
I'm using Safari on OSX 10.6.6
When I click on the 'play' button on a youtube video it works fine the first time. The second time (and subsequent times) I click on the 'play' button it shows me the first video I saw. This is just for the metafilter 'in-page player. If I click through to the video everything is fine.
I'm using Safari on OSX 10.6.6
I've noticed the same thing occasionally in Chrome (on Ubuntu). I always assumed it was related to my having 40+ tabs open at the time.
posted by achmorrison at 7:45 AM on February 12, 2011
posted by achmorrison at 7:45 AM on February 12, 2011
I'm having difficulty recreating the bug now (though I did experience it a few times over the last few days so I know it wasn't once off).
posted by a womble is an active kind of sloth at 7:53 AM on February 12, 2011
posted by a womble is an active kind of sloth at 7:53 AM on February 12, 2011
This happens to me frequently (but not all the time) with Chrome (OS X 10.5.8).
posted by ddaavviidd at 11:03 AM on February 12, 2011
posted by ddaavviidd at 11:03 AM on February 12, 2011
This also happens very frequently for me; I use Chrome on OS X 10.6.6
posted by dcheeno at 11:05 AM on February 12, 2011
posted by dcheeno at 11:05 AM on February 12, 2011
This is a frustrating bug because in theory the internal player page should never be cached. The URL that pulls in the player contains a unique YouTube video ID and jQuery adds a random element to the querystring for good measure. So the browser should see it as something new each time. We even add a random element to the YouTube embed URL with each request in case it's something on their end.
I just added some extra HTTP headers to the internal player page that tells browsers: no really, don't cache this. Let's see if that helps things.
posted by pb (staff) at 11:31 AM on February 12, 2011
I just added some extra HTTP headers to the internal player page that tells browsers: no really, don't cache this. Let's see if that helps things.
posted by pb (staff) at 11:31 AM on February 12, 2011
Thanks pb, it looks like that fixed it for Safari anyway.
posted by a womble is an active kind of sloth at 10:26 AM on February 13, 2011
posted by a womble is an active kind of sloth at 10:26 AM on February 13, 2011
Update: In this thread http://www.metafilter.com/100752/Anonymous-warns-Westboro-Baptist-Church-stop-now-or-else
I got the same problem again that I had previously with this comment:
http://www.metafilter.com/100752/Anonymous-warns-Westboro-Baptist-Church-stop-now-or-else#3531689
posted by a womble is an active kind of sloth at 12:02 PM on February 20, 2011
I got the same problem again that I had previously with this comment:
http://www.metafilter.com/100752/Anonymous-warns-Westboro-Baptist-Church-stop-now-or-else#3531689
posted by a womble is an active kind of sloth at 12:02 PM on February 20, 2011
Does a page refresh fix it? Or does it happen every time?
posted by pb (staff) at 12:10 PM on February 20, 2011
posted by pb (staff) at 12:10 PM on February 20, 2011
It's strange, I can't recreate the problem now. I can't remember whether a page refresh fixed it or not, sorry (I remember trying it though!).
posted by a womble is an active kind of sloth at 10:23 AM on February 24, 2011
posted by a womble is an active kind of sloth at 10:23 AM on February 24, 2011
You are not logged in, either login or create an account to post comments
posted by mathowie (staff) at 7:40 AM on February 12, 2011