Takahiro
Takahiro
I think it's helpful to users if we describe what browsers are supported. I confirmed it works on Firefox/Chrome and doesn't work on Edge/IE11 so far. I haven't tried other...
Related #60 Currently immersive-custom-elements don't work on some browsers for example Edge. But Google`s model-viewer seems to work on some of them. I suppose that's because they use some polyfills....
Related #60 It may be useful to display message like "immersive-custom-elements are not supported on your browser" for non-compatible browsers.
From #67. Fullscreen API on iOS for mobile seems to have limitation. Helpful if we add a note about it.
This issue follows #61 With #61, we request contributors to send PR to dev branch, not master branch. It's helpful to add contribution guide for contributors which describes the branches...
`` seems unstable on Firefox Reality + OculusGo. The problems I faced are - Sometimes video doesn't play smoothly - Always no loop back I checked console log but nothing...
Brainstorming thread. Feel free to write anything about new custom elements ideas. I open an individual issue "implement \" if the idea looks nice to go.
Most of the code expects input is always valid and doesn't do proper error handling, for example image/video src is always valid and can be loaded fine. We should do...
Currently `immersive-custom-elements.js` is > 1MB and `immersive-custom-elements.min.js` is > 500KB. They may be too big just for the simple interactive 360 image/video contents. I think the majority of the files...
To indicate on loading to users.