You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Mobile browsers have had limitations playing inline video.
107
+
Mobile and now desktop browsers have limitations playing inline video.
108
108
109
109
Because of an [iOS platform restriction][iosvideo] in order to get inline video
110
110
(with or without autoplay), we must:
@@ -113,15 +113,19 @@ Because of an [iOS platform restriction][iosvideo] in order to get inline video
113
113
- Set the `playsinline` attribute to the video element (is automatically added to all videos).
114
114
- Possibly pin the webpage to the homescreen for older iOS versions.
115
115
116
-
Inline video support on iOS 10 may change this. On certain Android devices or
117
-
browsers, we must:
116
+
Mobile and desktop browsers have been tightening the video autoplay policies to preserve battery and avoid intrusive advertisements. Most browsers now require a user action (such as a click or tap event) to start video playback:
Lately, there has been improving support. We do not focus too much on video,
124
-
but below are GitHub issues that may contain helpful information from community:
126
+
There's an [A-Frame example that includes the necessary logic][video-playback-example] to request the user clicking or tapping to start video playback. [The source code is also available][video-playback-code]
127
+
128
+
We do not focus too much on video, but below are GitHub issues that may contain helpful information from community:
125
129
126
130
-[*Videos and videospheres don't work on mobile*](https://github.com/aframevr/aframe/issues/316)
127
131
-[*Document iOS video encoding restrictions*](https://github.com/aframevr/aframe/issues/1846)
@@ -329,6 +333,6 @@ Phones with Adreno 300 series GPUs are notoriously problematic. Set [renderer pr
329
333
330
334
## Why is the gyroscope / magic window mode not working?
331
335
332
-
[New browser policies](https://www.w3.org/TR/orientation-event/#dom-deviceorientationevent-requestpermission) require sites to prompt the user for permission before getting access to DeviceMotionEvents. [Starting with iOS 13](https://webkit.org/blog/9674/new-webkit-features-in-safari-13/) DeviceMotionEvents are only available for pages served over `https`. Other browsers will also apply same policies and restrictions. A-Frame now [incorporates customizable UI](https://aframe.io/docs/1.0.0/components/device-orientation-permission-ui.html#sidebar) to request the necessary permissions to the user. Make sure to update to [A-Frame latest version](https://github.com/aframevr/aframe/releases)
336
+
[New browser policies](https://www.w3.org/TR/orientation-event/#dom-deviceorientationevent-requestpermission) require sites to prompt the user for permission before getting access to DeviceMotionEvents. [Starting with iOS 13](https://webkit.org/blog/9674/new-webkit-features-in-safari-13/) DeviceMotionEvents are only available for pages served over `https`. Other browsers will also apply same policies and restrictions. A-Frame now [incorporates customizable UI](https://aframe.io/docs/1.0.0/components/device-orientation-permission-ui.html#sidebar) to request the necessary permissions to the user. Make sure to update to [A-Frame latest version](https://github.com/aframevr/aframe/releases)
0 commit comments