[webvr] Why does entering VR need to be on user interaction?
flux.blackcat at gmail.com
Thu Sep 22 19:57:53 UTC 2016
1. Visite some site (an ordinary web page)
2. It has a link of the form <a href="vr-thingy.html">Try this VR thingy
3. You click the link, you land on a different page, whose sole purpose
is to do VR
4. You have to click "Enter VR Now" on that page to get into VR
I thought that was what Kip was talking about about 15 replies ago with
On Thu, Sep 22, 2016 at 8:47 AM, Brandon Jones <bajones at google.com> wrote:
> On Thu, Sep 22, 2016, 2:18 AM Florian Bösch <pyalot at gmail.com> wrote:
>> I believe there is a situation in which the user interaction to enter
>> WebVR requirement might not be intuitive.
>> 1. Visite some site (an ordinary web page)
>> 2. It has a link of the form <a href="vr-thingy.html">Try this VR
>> thingy here</a>
>> 3. You click the link, you land on a different page, whose sole
>> purpose is to do VR
>> 4. You have to click "Enter VR Now" on that page to get into VR
>> It could be argued that user intent to enter VR was already decided on
>> step #3 with a single click.
> This is definitely an interesting use case to consider. I've want to
> discuss it with the other implementors, but it doesn't seem too
> I guess it largely comes down to trying to infer the users context. If I'm
> already viewing WebVR content and I link to new WebVR content it's highly
> likely that I want to see the new page in VR immediately. The assumption
> coming from the other side is that if I'm not in VR yet it's (especially at
> this point) a pretty safe bet that I don't want to be accidentally tossed
> into VR. The "link as a user gesture" concept straddles those two
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the web-vr-discuss