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
It would be nice to have Android Intents supported in Samsung Internet Browser.
My specific use case is I want a user on 2D mobile be able to click the "Enter VR" button on an A-Frame WebVR site, and have that trigger opening the Samsung Internet Browser in Gear VR mode.
In order to intercept that click, an Android Intent would need to be registered for the Samsung Internet Browser Android app, as well as a JavaScript protocol (intent://):
The text was updated successfully, but these errors were encountered:
cvan
changed the title
support Web Intents for deep-linking to Samsung Internet Browser on Gear VR
support Android Intents for deep-linking URLs in Samsung Internet Browser on Gear VR
Sep 26, 2017
To open the GearVR browser specifically the intent should probably be something like: intent://#Intent;package=com.sec.android.app.svrbrowser;S.uri=https://aframe.io/aframe/examples/showcase/spheres-and-fog/;end
The ovrweb:// protocol will open what ever browse the user has set as default which is usually the Occulus browser but can be set to Samsung Internet for GearVR. I am looking for more info into intents.
@bluemarvin, colleague and Gecko platform Engineer, might be able to point you in the right direction. He implemented this recently for a special build of Gecko for Android.
It would be nice to have Android Intents supported in Samsung Internet Browser.
My specific use case is I want a user on 2D mobile be able to click the "Enter VR" button on an A-Frame WebVR site, and have that trigger opening the Samsung Internet Browser in Gear VR mode.
In order to intercept that click, an Android Intent would need to be registered for the Samsung Internet Browser Android app, as well as a JavaScript protocol (
intent://
):Here are the docs for Android Intents with Chrome, which works today in Chrome for Android.
See the discussion in this Twitter thread: https://twitter.com/cvanw/status/910428329114689536
Related reading:
The text was updated successfully, but these errors were encountered: