I have observed a strange problem on my HTML5 web application on IE 10 windows 7. The problem occurs when sliding the thumb of the video player, or clicking +30s or -30s numerous times the browser freezes and after sometime the message box to "recover page" comes.
Related
I am working on a web page for a company which is only going to run on company internal iPad's that loads .mp4 videos. The iPad's are using the ios Safari browser in full screen mode (locked) to open a URL which contains a link to the videos. When the web page loads it displays a spinning wheel for a few seconds which the video, I assume is still being downloaded.
Is there a way I can prevent/hide that spinning wheel?
The site I am working on is using some code from its previous website from a few years ago. The audio player doesn't load in firefox (click the listen button, audio player will open in popup). I think it's using jw player.
It's fine in Chrome but in Firefox it just doesn't appear. Any idea why?
That site use jwplayer 5 (very old), so the player needs Flash player correctly activated on Firefox (https://helpx.adobe.com/it/flash-player/kb/enabling-flash-player-firefox.html)
On Chrome, maybe you have the flash player blocked (by default with new Chrome versions) and the player fallback to mp3 file, or the flash plugin is correctly activated on Firefox
I've got a quick n dirty trial here,
<body>
TEST
<audio src="preview1.mp3" id="audio"></audio>
</body>
Then in my javascript console on desktop, I do the following:
var audio = document.getElementById('audio');
audio.play(); // the first audio plays just fine!
audio.pause();
audio.src = 'preview2.mp3';
audio.play(); // the second audio plays fine, too!
However, when I do the exact same thing on any mobile device (specifically iOS and Android devices are the ones that I've tried), absolutely nothing happens. No audio plays at all.
I've done a ton of searching online but it doesn't seem to be the case for anybody else?
Thoughts?
If you are having trouble with your audio player, please note that in Safari on iOS (for all devices, including iPad), where the user may be on a cellular network and be charged per data unit, preload and autoplay are disabled by the iOS. No data is loaded until the user initiates it. This means that the audio player is inactive until the user initiates playback by clicking on the play button.
For Android devices:
Chrome does not allow applications to play HTML5 audio without an explicit action by the user, similar to how it is handled by iOS, but differently than how the stock Android browser handles it.
Reference: http://www.wix.com/support/html5/technical-difficulties/browser-compatibility/faq/my-video-is-not-playing-on-my
On iOS and desktop I don't have problems playing my HTML5 audio with audio.js – everything works fine. But with Android the play-button needs three taps to play!
I've also written a issue about this on audio.js' github: https://github.com/kolber/audiojs/issues/177
REPRO:
go to http://kolber.github.io/audiojs/ on a Android phone (I tested with Xperia Z1/Android 4.4.2)
expected the play/pause button to be in play state initally, but is in loading state
clicking play makes the button go into play state
clicking again sets the button into loading state
clicking again sets the button into playing state, and this time finally plays the audio!
How can I make it play with only one tap/click??
I'm building a mobile site in which in embed some youtube videos with the IFrame player API (https://developers.google.com/youtube/iframe_api_reference).
Basically, I need to start this video after the user clicks a custom play button. This button triggers the player.playVideo() on the loaded youtube iframe to play the video. This works fine on the standard android and iphone browser (video starts playing fullscreen). However in Google Chrome's mobile browser (android and ios) I get a second play button over the video after my first click, thus making me click twice to play the video.
Anyone know a workaround for this?
Theoretically the autoplay is disabled on Safari and Google Chrome for Android . In my experience I never could avoid to show the second button with Youtube player API, even with an action triggered by user (the first click).