-
-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Entering into fullscreen mode on iPhone is broken #6
Comments
I don't have an IOS device, so I can't clearly know what happened from your description. Can you tell me more details ? |
Ok let me try to explain better, step-by-step:
If you want me to try and catch a video or screenshot, I can try that too. |
Same goes for the exit from the full screen mode. |
catch a video or screenshot. |
Console errors are the ones that I posted in the first message:
|
yes, I had to click this button to go into full screen, the one bellow (dashed square) works directly on the Mac (Shrome/Safari) |
This error message indicates that I can't locate the source code. Is it convenient to run the program in the debugger mode to trace the source code? Or wait for me to generate the sourcemap. |
@phpb-com Try it again |
Some more logs from the console, if it helps:
|
Just to note, the current deployment to you demo is not crashing any longer. |
I guess ios on the full screen may also need some prerequisites, like autoplay, you need to set mute to be able to. Because on oplayer.vercel.app isFullscreenEnabled gets false. |
That is OK, autoplay on almost all modern browsers requires for you to set mute to work, or to be triggered by user actions. I would not worry about that, autoplay works when it has to. Fullscreen on iPhone devices is a trickier one. This one does not work on Edge, Chrome, Safari on iPhone latest iOS. fullscreenWeb does work, but it only enlarges video element to the full viewportal of the browser window. |
Ios can't do full screen for non-video tags, but if I put video full screen, the subtitle and danmaku will not follow the display, which is a problem. |
Yes, I figured as much. Basically, it is only native interface in full screen mode. Maybe add a setting to allow user to switch it on with the caveat that danmaku like plugins will stop working? |
Any chance you are going to cut a new release. I assume you made it that only fullscreenweb is available on iPhone. The one that is on your demo site seems to have it working as expected with fullscreenweb |
I found that IOS safari status is not synchronized with other platforms. reply #7 |
for this issues. On IOS safari fullscreen used video element. |
That is interesting, I knew that iOS always wants to be special ;-) |
I find a lot of unintended behavior on IOS. lol |
iOS is more like lolOS, but a big portion of people are using it so we have to deal with it :-( I tried your demo site just now, all seems to be working as expected on iPhone. Would be great if you could cut a fresh release with all of the improvements that you just made. Huge thanks! |
If you change the progress bar before clicking the play button and then click play, it will behave in many strange ways |
timeupdate seeked etc. will not trigger |
1.0.21 seems to work as expected, thanks for so much updates in such a short time. If you have a "beer" account where I could donate as a token of appreciation, let me know. :-) |
This is the error from the Web Inspector console:
[Error] TypeError: undefined is not an object (evaluating 'o(this, T, U).call')
enterFullscreen (chunk-KSDSIAZN.js:390)
toggleFullScreen (chunk-KSDSIAZN.js:399)
oplayer/packages/core/src/player.ts
Line 237 in f0bf039
The tooltip that pops-up after the click, brings the video into semi-fullscreen that only expands into the browser window, not the true full screen. I think that it is due to the playsinline setting. I know that VideoJS is working well, but I think that they remove the playes inline prop from the video attribute when the user clicks the full screen switch. And they put it back, when the screen is returned to normal.
The text was updated successfully, but these errors were encountered: