Closed Bug 1271157 Opened 8 years ago Closed 6 years ago

Cannot drag scroll image on certain site

Categories

(Web Compatibility :: Site Reports, defect, P3)

Firefox 46
Unspecified
Windows 10
defect

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: alice0775, Unassigned)

References

()

Details

(Keywords: regression, Whiteboard: [country-all][needscontact])

Original report : See http://forums.mozillazine.org/viewtopic.php?p=14597105#p14597105

Steps to reproduce:
1. Open http://www.geforce.com/hardware/technol ... ge-gallery
2. Click small + icon in thumbnail image
3. Mouse drag over image

Actual Results:
I can't scroll around

Expected Results:
Image should be scrolled

Regression window:
https://hg.mozilla.org/integration/mozilla-inbound/pushloghtml?fromchange=a4d42eb9721db2302b0cb4310e7049c8a9299abf&tochange=591f1064b73c05bc20f18801c1c369dc3403d0d2

Triggered by: 591f1064b73c	Kearwood (Kip) Gilbert — Bug 1218482 - Enable WebVR By Default,r=bz

And confirm that it works if set dom.vr.enabled = false.
Flags: needinfo?(kgilbert)
Whiteboard: gfx-noted
Not to nit pick but isn't the problem the image can't be panned?
This site appears to be detecting the browser as WebVR enabled, but expecting to enter VR even if you don't have a headset connected.  The reason you can't pan with your mouse is that the site is expecting you to be wearing a headset and to be turning your head.

The site should be updated to not expect a WebVR capable browser to have a headset detected.  Perhaps the MozVR team at Mozilla could help.  Ideally, the site will be updated to use the WebVR 1.0 API in the process.

I'll NI Casey and see if we have some cycles to help them out.
Flags: needinfo?(kgilbert) → needinfo?(caseyyee.ca)
Component: Graphics → Desktop
Product: Core → Tech Evangelism
Whiteboard: gfx-noted
Version: Trunk → Firefox 46
(In reply to :kip (Kearwood Gilbert) from comment #3)
> This site appears to be detecting the browser as WebVR enabled, but
> expecting to enter VR even if you don't have a headset connected.  The
> reason you can't pan with your mouse is that the site is expecting you to be
> wearing a headset and to be turning your head.

http://images.nvidia.com/ansel/build/vrview-analytics.min.js

5: [function(_dereq_, module, exports) {
  var WebVRPolyfill = _dereq_("./webvr-polyfill.js");
  window.WebVRConfig = window.WebVRConfig || {},
  new WebVRPolyfill
}

function WebVRPolyfill() {
  this.devices = [],
  this.isWebVRAvailable() || this.enablePolyfill()
}

WebVRPolyfill.prototype.isWebVRAvailable = function() {
  return "getVRDevices"in navigator || "mozGetVRDevices"in navigator
}

Yeah, so they assume just having the interface means there's a connected device. They should update their code to actually check for devices w/ navigator.getVRDevices, and then enable the polyfill (which appears to enable mouse panning) if not.
Whiteboard: [country-all][needscontact]
OK, so I gave this a try.  It will work properly and you can pan the image when dom.vr.enabled = false in Nightly.  

As per Kip, this is due to expecting orientation from the headset -- which will override any mouse-look function in the view.

Thee solution is to update vrview to continue to allowing panning if the headset is not connected or returning proper pose information.
Flags: needinfo?(caseyyee.ca)
Also, more information about vrview is here: https://developers.google.com/vr/concepts/vrview
Priority: -- → P3
Casey - sorry that I missed this. Do you know if the issue still exists?
Flags: needinfo?(caseyyee.ca)
Adam, I don't think that this issue is something we can solve.  Also, latest updates to API don't allow for tracking of the headset pose unless user has entered VR.  In any case, this is a bug in VR view and it's up to them to fix it and not anything we can do from Firefox to fix this issue.
Flags: needinfo?(caseyyee.ca)
Update: I spoke with Casey on Slack, he re-tested this and found "it doesn't appear to be an issue at all anymore."

Closing the report as fixed.
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
Product: Tech Evangelism → Web Compatibility
You need to log in before you can comment on or make changes to this bug.