<files-triage>

The interesting corner case:
(1) Put device in clamshell mode.
(2) Save a file from the browser or similar
(3) The "Save as" window opens without the soft keyboard out. "Filename" input element has a focus (the bold underline)
(4) Put device in tablet mode while "Filename" has a focus
(5) The on screen keyboard should pop-up *
(6) User should be able to cut/paste text selection with blue touch handles *

* = Doesn't happen.

in M70 dev on eve:

#12 step 5) when the device is in tablet mode, focus the input element with touch and ... the on-screen keyboard pops-up.

In M70 dev on eve:

(1) Put device in tablet mode
(2) Save a file from the browser or some other app (Text in my case)
 (2a) save dialog appears
(3) focus the "save as" field on the dialog using touch
 (3b) the on-screen keyboard appears
(4) enter the file name using the the on-screen keyboard
(5) the file is save with that name

In M70 dev on eve:

1) Open Files app in tablet mode.
2) use 2 finger press on a file
 2a) the file context menu is shown
3)_Select the "rename" context menu
 3a) a text input field appears
4) touch that input field
 4a) the on-screen keyboard appears

Seems like this issue has been fixed, outside of Files App as expected. 

The component layers of chrome deal with special assist for WebContent (web pages, chrome extensions, or apps) input elements.

I can still repro the original but on Kevin M70. 

When I filed this my opinion was that the keyboard should open automatically. I no longer think that is true, the user should be able to save whatever default file name if they would like. However, when the keyboard opens it automatically pushes the file picker window up (it looks like) so I can no longer see the top of the window which is where the directory tree is. 

Could we overlay the soft keyboard without moving the place in the file picker?

> I can still repro the original but on Kevin M70. 

Tried on Kevin and no repro for me.  Still not working for you?

>When I filed this my opinion was that the keyboard should open automatically. I no longer think that is true, the user should be able to save whatever default file name if they would like.

https://cs.chromium.org/chromium/src/content/renderer/render_widget.cc?rcl=75dd162683c8885834e075778314451ce5ee23ca&l=2110

  // On ChromeOS, virtual keyboard is triggered only when users leave the
  // mouse button or the finger and a text input element is focused at that
  // time. Focus event itself shouldn't trigger virtual keyboard.

What this means is that Blink must be processing a user gesture: mouse up, or tap up, and there is focused <input> element on the web page.

https://cs.chromium.org/chromium/src/content/renderer/input/render_widget_input_handler.cc?rcl=a29d09e5d5b9b8ca261f4e2c84a9f77eb4d03a12&l=426

so user needs to tap or click.

> However, when the keyboard opens it automatically pushes the file picker window up (it looks like) so I can no longer see the top of the window which is where the directory tree is.

Yes, it scrolls the <input> element into view so the user can type a file name :)

> Could we overlay the soft keyboard without moving the place in the file picker?

Maybe, but user would then need to manually scroll to bring the <input> into view, right?

Main thing I noticed was not one test squeaked.  Filed 879434 about adding some VK tests to cover the basics as in this report. 

Ahem issue 879434.

> However, when the keyboard opens it automatically pushes the file picker window up (it looks like) so I can no longer see the top of the window which is where the directory tree is.
Yes, it scrolls the <input> element into view so the user can type a file name :)

> Could we overlay the soft keyboard without moving the place in the file picker?
Maybe, but user would then need to manually scroll to bring the <input> into view, right?

Sure, that's fair. I suppose another way to put it is: When the VK is open the user should be able to see the <input> field as well as be able to access the tree directory (top of Files app) at the same time. Is there a way for us to achieve that? One part of "Save as" is to specify a file name, one is to choose the destination, it would be great if those were both equally accessible. 

+Weifang FYI and prioritization.