Inline player problem October 23, 2011 3:24 PM Subscribe
Can I get some confirmation that it's just me or not? On my iPad 1 and iPhone 4 (software version 5.0 on both) the inline video player displays incorrectly.
Instead of centring on the screen as it used to it now appears (or not) offset, depending on the orientation and not always in the same way. Screencaps - Portrait 1, Portrait 2 and Landscape. The problem seems to be related to how old the post is. For example, the Liszt videos display perfectly but if I scroll down to the bottom of the page and try to view the human slingshot video it's so far offset that I can't even see the player. This is only if I click the inline player link from the front page, the player performs correctly from within the post. It's the same deal for me on my iPhone. I did the contact form thing but I don't think my problem was quite understood without my screencaps to illustrate.
Instead of centring on the screen as it used to it now appears (or not) offset, depending on the orientation and not always in the same way. Screencaps - Portrait 1, Portrait 2 and Landscape. The problem seems to be related to how old the post is. For example, the Liszt videos display perfectly but if I scroll down to the bottom of the page and try to view the human slingshot video it's so far offset that I can't even see the player. This is only if I click the inline player link from the front page, the player performs correctly from within the post. It's the same deal for me on my iPhone. I did the contact form thing but I don't think my problem was quite understood without my screencaps to illustrate.
Note that it would be ok if you were able to scroll down and center it yourself, but you can't move the player at all.
posted by Threeway Handshake at 3:35 PM on October 23, 2011
posted by Threeway Handshake at 3:35 PM on October 23, 2011
Happens to me, too, on the same setup. But only on the front page proper. If I click in to the post, the inline player behaves appropriately.
posted by donnagirl at 3:45 PM on October 23, 2011
posted by donnagirl at 3:45 PM on October 23, 2011
I did the contact form thing but I don't think my problem was quite understood without my screencaps to illustrate.
Sorry, I misunderstood your report. It really helps if you include screenshots of the problem and a detailed description of what's happening. Yeah, looks like something is off, we'll take a look.
posted by pb (staff) at 4:15 PM on October 23, 2011 [1 favorite]
Sorry, I misunderstood your report. It really helps if you include screenshots of the problem and a detailed description of what's happening. Yeah, looks like something is off, we'll take a look.
posted by pb (staff) at 4:15 PM on October 23, 2011 [1 favorite]
7:15pm on a Sunday evening....that's some service.
posted by lazaruslong at 6:24 PM on October 23, 2011
posted by lazaruslong at 6:24 PM on October 23, 2011
How come awesome is good but awful is bad?
posted by Meatbomb at 9:50 PM on October 23, 2011 [1 favorite]
posted by Meatbomb at 9:50 PM on October 23, 2011 [1 favorite]
I just updated the inline player. It should work better now on iPads and iPhones. Let me know if not. Thanks for the heads up.
posted by pb (staff) at 10:20 PM on October 23, 2011
posted by pb (staff) at 10:20 PM on October 23, 2011
It's better but it's also different now. Clicking the player icon opens a new window (even from within the post). It used to be that you got the floating player in front of the comments. The 'Close Window' doesn't work either, you have to hit the back button to return to the post (twice, if you click the Close Window first).
posted by unliteral at 10:45 PM on October 23, 2011
posted by unliteral at 10:45 PM on October 23, 2011
Sounds like something is still off. You shouldn't get a new window. Taking a look.
posted by pb (staff) at 10:48 PM on October 23, 2011
posted by pb (staff) at 10:48 PM on October 23, 2011
Everything is checking out ok for me on both iPads and iPhones. You might try clearing your cache and logging out and back in again. Try reloading the site and see if you're still having trouble.
posted by pb (staff) at 10:52 PM on October 23, 2011
posted by pb (staff) at 10:52 PM on October 23, 2011
The update involved a few files so if one of those new files didn't load it could bomb like that. Clearing your cache should force your browser to grab new copies of everything. Anyway, glad it's working now.
posted by pb (staff) at 11:06 PM on October 23, 2011
posted by pb (staff) at 11:06 PM on October 23, 2011
Oh! and sorry about the timing, it was Monday morning for me.
posted by unliteral at 11:09 PM on October 23, 2011
posted by unliteral at 11:09 PM on October 23, 2011
Were you asking if you could get a witness? I've been waiting years for the right occasion to say that.
posted by msalt at 11:18 PM on October 23, 2011
posted by msalt at 11:18 PM on October 23, 2011
How come awesome is good but awful is bad?
As it turns out, awe originally meant fear or dread. That’s an archaic usage now; as the OED puts it, “From its use in reference to the Divine Being [awe] passes gradually into: Dread mingled with veneration, reverential or respectful fear”. This in turn changes into “solemn and reverential wonder, tinged with latent fear,” which most closely approximates my personal take on the modern meaning of awe.posted by TheophileEscargot at 1:08 AM on October 24, 2011 [1 favorite]
Since the meaning of awe was changing, the meaning of word derived from awe depended a lot on when they were derived. Aw(e)ful entered the language fairly early on, while awe still was predominantly a type of fear, whereas awesome came along later (around the turn of the 17th century), after the dread had mostly filtered out of awe.
You are not logged in, either login or create an account to post comments
posted by Threeway Handshake at 3:32 PM on October 23, 2011