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

Issue 627029 link

Starred by 3 users

Issue metadata

Status: Verified
Owner:
Last visit > 30 days ago
Closed: Aug 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug-Regression



Sign in to add a comment

Focus is not shifting to next filter on clicking forward, backward arrows in Camera.app

Project Member Reported by sandeepk...@techmahindra.com, Jul 11 2016

Issue description

Version: 54.0.2792.0/8573.0.0 (Official Build) dev-channel Gnawty, Peppy, Daisy
OS: Chrome
What steps will reproduce the problem?
(1)Sign in to user>> go to Camera.app>> go to toggle filters>> try to click forward, backward arrows>> and observe

Expected: On-Clicking forward, backward arrows blue focus should be shifted to next filter
Actual: Instead focus is not shifting to next filter

This is a Regression as crash is not seen in M51: 51.0.2704.103/8172.60.0 -Stable-Channel Daisy

Issue is not applicable to Linux Windows
 
This is a Regression issue as issue is not seen in M51: 51.0.2704.103/8172.60.0 -Stable-Channel Daisy
Able to reproduce the issue on chrome(Peppy) using Version: 54.0.2792.0/8573.0.0.
Observed the focus is not moving to the next filter instead the scroll bar is moving left and right.

Cc: y...@chromium.org
Seems like a recent regression. I don't have it on 54.0.2787.0. I expect some temporary bug in Blink, as we didn't change anything recently in the Camera app.
Labels: -ReleaseBlock-Stable ReleaseBlock-Beta
It seems to be the scroll is very erratic and creating bad user experience, so increasing the priority by marking it as RB-Beta. Please feel free to edit or remove if this is not the case.

Comment 6 by y...@chromium.org, Jul 11 2016

Cc: -y...@chromium.org mtomasz@chromium.org
Owner: y...@chromium.org

Comment 7 by y...@chromium.org, Jul 11 2016

Camera app is still using the deprecated keyIdentifier (https://developer.mozilla.org/en-US/docs/Web/API/KeyboardEvent/keyIdentifier); I'll submit a fix.

Comment 9 by y...@chromium.org, Aug 1 2016

Cc: y...@chromium.org
Owner: rookrishna@chromium.org
Status: Fixed (was: Assigned)
Please help to verify the fix on go/cros-camera.
Status: Verified (was: Fixed)
Verified on Chome OS 54.0.2809.0/8650.0.0 samus 
Thanks for verifying. I'm going to push the new version today.
Project Member

Comment 13 by bugdroid, Today (11 hours ago)

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/d05463dc69133c53b49f5a530b2b83a8e0afc7e3

commit d05463dc69133c53b49f5a530b2b83a8e0afc7e3
Author: Yuli Huang <yuli@chromium.org>
Date: Tue Jul 19 05:25:21 2016

Support both KeyboardEvent keyIdentifier and key.

TEST=Tested manually on peppy.
BUG= chromium:627029 

Change-Id: I97a8c1a20a36ecfba2a45eaa57f8dfdade737c80
Reviewed-on: https://chromium-review.googlesource.com/360292
Reviewed-by: Tomasz Mikolajewski <mtomasz@chromium.org>
Tested-by: Yuli Huang <yuli@chromium.org>


Sign in to add a comment