Chrome Version: All
OS: Android/Windows/Linux/CrOS (any platform with touch)
What steps will reproduce the problem?
This is a code structure problem so there are many different problems.
Here is an example that is reproducible on Window/Linux/CrOS
(1) Long-press an empty input field (notice that the blue touch handle shows up)
(2) Move your mouse (notice the blue touch handle disappears)
(3) Long-press the empty input field (notice the blue touch handle isn't showing)

What is the expected result?
After the second long-press the touch handle was not shown.

What happens instead?
The touch handle should have reappeared.

The issue here is that when we move the mouse the handle is cleared in the browser [1] but not in the renderer. This means that the renderer (in particular the FrameSelection) still thinks the handle is present. When the user does a new long-press the renderer thinks there is no change in the selection [2] so it doesn't tell the browser to re-show the handle.

The underlying problem here is allowing the browser to change the selection handle visibility without notifying the renderer. I think the right solution is to send an IPC to the renderer to clear the handle and to get rid of the |show_touch_handles_| in |TouchSelectionController|. The problem with this solution is that |TouchSelectionController| wouldn't know which renderer to send the message to. mohsen@, do you have any ideas on this?

[1] https://cs.chromium.org/chromium/src/content/browser/renderer_host/input/touch_selection_controller_client_aura.cc?rcl=5a82fc5c7cda26056d495448b176a59fd0031e36&l=112

[2] https://cs.chromium.org/chromium/src/third_party/WebKit/Source/core/editing/SelectionController.cpp?rcl=2b2f89789e133c8904e505250e415699def7dea1&l=893