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

Issue 914741 link

Starred by 2 users

Issue metadata

Status: Assigned
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug-Regression



Sign in to add a comment

Regression : Unnecessarily Width value gets selected on clicking 'Resize' option in Files App Gallery

Project Member Reported by mmanchala@chromium.org, Dec 13

Issue description

Chrome Version: 72.0.3626.15/11316.18.0  Kip,Daisy  and  Reks,
OS: Chrome

What steps will reproduce the problem?
(1)Sign into User -> press 'Ctrl+F5(Overview Mode Button)' for screenshot -> go to Files App-> Right click for context menu and select 'Gallery'
(2)Now gallery will be seen ->click on 'Edit' option -> Click on 'Resize' option and observe Width value gets selected 
(Please refer Video and Screenshot)

Expected: Cursor should be available at 'Width' field
Actual: Instead Width value gets selected

This is Regression Issue as same is working fine on M-70 

Note : Issue is also seen on M-71 and M-73
 
Actual_TextSelected.mp4
11.9 MB View Download
Actual_Selection.jpg
92.3 KB View Download
Expected_Cursor.jpg
540 KB View Download
Expected_Cursor.mp4
9.8 MB View Download
Owner: adanilo@chromium.org
Status: Assigned (was: Untriaged)
Alex - can you please take a look at this one?
Status: Started (was: Assigned)
Sure, will try to reproduce now.
Owner: steve...@chromium.org
This regression is caused by changes to cr-input from https://bugs.chromium.org/p/chromium/issues/detail?id=882612 Assigning this to stevenjb@ for triage.
Cc: scottchen@chromium.org
Cc: dpa...@chromium.org
Labels: -Pri-1 Pri-2
Status: WontFix (was: Started)
This looks WAI to me? i.e. the change referenced in comment #3 was a fix for unintended behavior.

No, the expected behavior is focus on the width field, i.e. a visible cursor, not selection of the entire value. The change that explicitly calls 'select()' is the cause of this issue as described (i.e. "Width value gets selected"). It should be possible to call focus() without the select() side-effect. I agree it's WAI if tabbing to the input field, but our implementation is calling focus() directly.
Status: Assigned (was: WontFix)
Updating status per Comment #6.

Sign in to add a comment