New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 669922 link

Starred by 4 users

Issue metadata

Status: Fixed
Owner:
Last visit > 30 days ago
Closed: Oct 2017
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 2
Type: Bug
Proj-VR
Proj-XR
Proj-XR-VR



Sign in to add a comment

Disable pull down to refresh for VR Shell (or build some UI around it?)

Project Member Reported by mthiesse@chromium.org, Nov 30 2016

Issue description

Since we have no visual indicator for pull to refresh in VR Shell, it's pretty confusing when the page seemingly suddenly refreshes while scrolling. We should either disable that, or build some UI around it to make it clear what's happening.

 
Labels: Proj-VR-Daydream
Labels: -Proj-VR-Daydream Proj-VR-Shell OS-Android
Labels: VR-DF
Labels: -M-57

Comment 5 by xing...@intel.com, Dec 7 2016

Does you mean disable it in the web page or in the vr shell(After click Enter VR) ?

Pull to refresh works in the web page. But when click Enter VR and into the vr shell, I found no way to trigger this(nexus 6p/Andorid 7.0).
In order to trigger pull to refresh in VR Shell, you need a daydream view and controller, so that you can scroll the page with the touchpad while in VR Shell.
Labels: -VR-DF VR-Triage-Discuss
Owner: asimjour@chromium.org
Status: Assigned (was: Available)
Amir, based on the list of UI features we've disabled and need to reimplement in VR, can this be closed?  If so, could you close this off?
Labels: -VR-Triage-Discuss
Status: WontFix (was: Assigned)
It doesn't happen anymore.

Could I suggest closing this as *fixed* rather than *WontFix* as the underlying problem appears to have, in fact, and quite uncharacteristically, I'll add, *actually been fixed*?

For which I, uncharacteristically, thank you.
Just a note:  it's come to my attention that there may or may not be individual web applications, from various vendors, which still implement a  pull-to-refresh action.

Given that this might reasonably be attributed to Chrome itself by a user, I'd strongly recommend that this practice be _strongly_ deprecated.

Including any and all instances of Google systems implementing this, if any.
Status: Fixed (was: WontFix)
Thanks.
Labels: Test-Complete

Sign in to add a comment