So, I was reading through the simplified category styles thread, got to this post and was like “ooh, Dr. Mario, I’ll watch that.” And then I clicked on the Maximize button within the Youtube player so that I could see it in full screen majesty… and then Chrome 40.0.2214.93 had a little seizure and threw me back about 60 posts within the thread.
Subsequent to that hitch, pressing end took me back to the bottom of the thread, and then I couldn’t navigate any further in the thread at all, either via PageUp or UpArrow or mouse scroll wheel. The scroll bar in the right side of my browser was also completely gone.
Reloading the tab seems to have restored functionality, but I have a 100% reproduction rate on the above steps & symptoms.
Though I guess the reproduction is less than 100% with Chrome 40.0.2214.94. I did not reproduce once on initial reload after Chrome updated, but then did reproduce after going back to the tab after posting here to update my initial post.
I clicked on the video and then on the maximize button, the video went fullscreen just fine, after pressing the escape key I was also thrown back by ~50 posts or so, I’m on Chrome Version 41.0.2272.35 beta-m (64-bit).
Yes I get this bug as well. Not sure if it is Youtube or something else. I tried searching for anyone having a similar issue (on Google) and didn’t find anything.
Then Esc or close the fullscreen. Chrome jumps back 5 to 20+ posts. As Riking says, the earliest loaded post. On a long thread this can be hundreds of posts.
If you try to fullscreen again, it will (sometimes) instantly exit the fullscreen, and jump posts as before. For me this only happens on a second or third try, could be any video on the page.
I’d add more examples but I can’t find any here on Meta. Short topics don’t have this problem, and most Youtubes here on Meta seem to be in the first couple of posts.
Plenty of examples on my Discourse instance if needed. One very long topic with tons of Youtube posts is found here.
I can confirm this problem occurs for me on Windows 10 in both Chrome 49.0.2623.28 and IE 11.
It does not occur in Firefox 44.
EDIT #1:
Experienced this problem 3 times in the last 10 minutes.
Note to self: don’t click the bloody full-screen button until this is fixed !
If I was only trying to watch funny cat videos it wouldn’t bother me as much.
I was able to reproduce and what seems to be happening is Chrome briefly resizes the discourse window beneath to fullscreen before applying the video. I’m pretty sure it’s this bug which has been around for over a year
In terms of a workaround, I don’t think there’s anything we can do as the fullscreen code is triggered within the iframe, which is outside of our security context.
I still hope the Discourse team will find a workaround on this. My stance is that websites should adapt to the browsers behavior, especially the popular ones.
We are managing a video games community and this is the most annoying bug for our users right now.
videos it wouldn’t bother me as much.
