In simple terms and I'm guessing somewhat, but .... there's a transition to HTML5 with Youtube (and other video hosting sites), in how they handle videos that other sites embed within their own content. In our case, we try to convert a YouTube link to permit viewing in-line within posts, instead of having to leave the site and go to YouTube's site to view it.
The other factor is how various browser types choose to handle and interpret the coding they are reading when viewing a video being displayed on a web site. FireFox was working fine, whereas Chrome, Safari and Internet Explorer haven't handled the HTML5 transition in a smooth way.
This code we just installed is an update to the code we previously used. This new code outputs iframe embedding code, which is the YouTube-preferred embedding method. This allows either the HTML5 player or Flash player to be used, depending on the browser's capabilities. In other words, it handles the old and the new methods, compensating for Chrome, Safari and Internet Explorer's need to worry about it internally themselves.
The old code used flash object embedding code, which is deprecated by YouTube as of 2015. It couldn't be used in native mode on those browsers, except for FireFox which handled the conversion internally itself (I think..).
Anyway, things should work well again, at least until some new standard comes out and we have to chase a fix all over again ..
Regards,
DougInformation
![]()
Warning: This is a relatively older thread
This discussion is older than 360 days. Some information contained in it may no longer be current.