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

Issue 808488 link

Starred by 3 users

Issue metadata

Status: Duplicate
Owner:
Closed: Mar 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 2
Type: Bug
Proj-VR
Proj-XR
Proj-XR-VR



Sign in to add a comment

A magnifier-like UI appears but isn't magnified

Project Member Reported by dbbrooks@chromium.org, Feb 2 2018

Issue description

Chrome Version: 66.0.3336.0
OS: Android N, O
Device: Galaxy S8+, Pixel 2 XL

Note that this is a bit difficult to repro. I had to click in many places after initially seeeing this to get it to appear again.

What steps will reproduce the problem?
(1) Go to http://chrome-vr-test.appspot.com/
(2) Place device in Daydream headset, to enter Chrome VR
(3) Select in-between or close to some group of links. (My best guess)
(4) If you click in the right spot, a magnifier -like UI appears.

What is the expected result? Well, I'm just not 100% sure what this UI is. My guess is its meant to magnify a section. If so then I think it needs to be zoomed in, which it isn't.

What happens instead? See screenshot. No zoom in the magnifier-like UI.
 
Screenshot_20180201-171854.png
702 KB View Download
Cc: asimjour@chromium.org
Cc: mthiesse@chromium.org
This is chrome's touch disambiguation where we can't tell what the user tried to click on so we zoom it up to make it easier. I think we should hold off on doing anything until we change the input method cause it may fix it? I don't know enough about this space so I'm really just speculating

Amir/Michael: feel free to disagree :)
Labels: M-66
Status: Available (was: Untriaged)
Marking it as available. Please mark it as won't fix if we don't mind this behavior for now.
I think we should keep this open for now
Owner: mthiesse@chromium.org
Status: Assigned (was: Available)
Michael, can you take a look at this?
Labels: -M-66 FoundIn-66 M-67 Hotlist-VRB-MVP
I don't think this is worth merging back to 66, I'll fix for 67.
Owner: dbbrooks@chromium.org
Actually I can't get this to come up at all. I expect this was fixed by Amir in https://chromium-review.googlesource.com/c/chromium/src/+/949622.

Would suggest closing as Fixed if you can't repro this anymore David.
Labels: -M-67 M-66
we could consider merging that back to m66. The question is how much does this over-trigger there vs the risk of the change
Mergedinto: 817055
Status: Duplicate (was: Assigned)
Not going to merge back to 66, and this is already fixed in 67.

Sign in to add a comment