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

Issue 762664 link

Starred by 1 user
Status: Available
Owner: ----
Cc:
omrilio@chromium.org
█ oka@chromium.org
█ blakeo@chromium.org
█ mcirimele@chromium.org
yhanada@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug

Blocked on:
issue 642513

Participants' hotlists:
Fixing-touch

Show other hotlists

Other hotlists containing this issue:
Hotlist-Files-Touch


Sign in to add a comment

Open soft keyboard for new folder textfield in tablet mode

Project Member Reported by mcirimele@chromium.org, Sep 6 2017 
Chrome Version: 63.0.3206.0 9916.0.0 Kevin

What steps will reproduce the problem?
(1) Put device in tablet/touch mode
(2) Create a new folder

What is the expected result?
The folder is created and the soft keyboard opens automatically to allow users to type the name of the folder. 

What happens instead?
The soft keyboard does not open. When I tap the textfield to open the keyboard the text is selected and two menus appear. 

Video: https://drive.google.com/open?id=0B-PpvprrWoupTWlzZndVWDFYemM

Comment 1 by fukino@chromium.org, Sep 22 2017

Cc: yhanada@chromium.org oka@chromium.org
+oka@, +yhanada@,

In the scenario seen in the Video, Files app create text input (<input> tag) and the input tag is focused by script, not by user input.
Can we open virtual keyboard in this case?

Comment 2 by oka@chromium.org, Sep 22 2017

Cc: omrilio@chromium.org blakeo@chromium.org
Hmm. I think there's no way to explicitly show keyboard if the input focus is asynchronously happens after user's tap.
If somewhere is focused after tap event handler returns, it will open virtual keyboard.

Comment 3 by oka@chromium.org, Sep 22 2017 

Sorry typo:  s/after/before/ in #2.
If somewhere is focused **before** tap event handler returns, it will open virtual keyboard.

Comment 4 by oka@chromium.org, Sep 27 2017

Blockedon: 642513

Comment 5 by weifangsun@chromium.org, Nov 16 2017

Labels: -M-63 M-65

Comment 6 by weifangsun@chromium.org, Jan 30 2018

Labels: -M-65 M-66

Comment 7 by weifangsun@chromium.org, Feb 7 2018

Owner: ----
Status: Available (was: Untriaged)

Comment 8 by sashab@chromium.org, Feb 16 2018

Labels: CrOS-FilesApp-Touch
<files-triage>

Comment 9 by sashab@chromium.org, Feb 28 2018

Labels: -CrOS-FilesApp-Touch CrOSFilesCategory-Touch

Comment 10 by weifangsun@chromium.org, Feb 28 2018

Labels: M-69

Comment 11 by weifangsun@chromium.org, Feb 28 2018

Labels: -M-66

Comment 12 by loyso@chromium.org, Apr 9 2018

Labels: -Pri-3 OS-Chrome Pri-2

Comment 13 by slangley@chromium.org, Jun 21 2018

Owner: noel@chromium.org
Status: Assigned (was: Available)

Comment 14 by weifangsun@chromium.org, Aug 8

Labels: -Pri-2 -M-69 M-70 Pri-1

Comment 15 by weifangsun@chromium.org, Sep 27

Labels: -M-70 M-71

Comment 16 by mcirimele@chromium.org, Oct 12 

Reproduced on 71.0.3572.0 (Kevin) today. 

When the folder is created the text field should be in focus with the default name highlight and ready to be overwritten. In touch mode that means we should also have the VK open. 

When the folder is created in touch mode it shows an empty string for the name. We should show the default "New folder" string. Filed  issue 894971  to update that string to sentence case.

Comment 17 by slangley@chromium.org, Nov 12

Labels: -M-71 M-72

Comment 18 by noel@chromium.org, Nov 12

Owner: ----
Status: Available (was: Assigned)
Seems the linked bug should be resolved first: unassigned and removing milestone until issue 642513 is resolved.

Comment 19 by noel@chromium.org, Nov 12

Labels: -M-72
►

Sign in to add a comment