azurewei@, can you please take a look? This is possibly fixed by some of your in-progress changes.

I should also note that on 57.0.2925.0 canary when I plug in an external keyboard and enter touchview mode I don't actually see the VK toggle appear in the IME detailed view. Possibly a separate bug?

One of my pending CL should fix this bug, which is verified on Clapper.

I cannot repo the bug of 'VK toggle not appear' with latest build.

Thanks, for reference the CL described in #3 is https://chromiumcodereview.appspot.com/2521443002/.

Regarding the toggle not appearing at all: I will file a separate bug for that if I see it happen again once your changes have landed.

Sorry, misunderstood the bug in my last comments. 
By 'special toggle row turns back off' do you mean the VK toggle is invisible or with 'off' state? Could you give a screenshot?

If it means the VK toggle is invisible, I cannot repo the bug on  57.0.29208.0 canary.

If it means the VK toggle is with 'off' state, it's by designed. When plunging in an external keyboard, the default touch keyboard will be disabled. Thus the 'On-screen keyboard' toggle button shows the touch VK state (off) to let users could enable it again.  
 

pbathini@, I'm handing back to you to clarify the bug repro steps or whether this bug is still valid. I tried the following on the latest canary (57.0.2926.0):

1. Enter touchview and plug in an external keyboard.
2. Open the IME detailed view.
3. Set the 'on screen keyboard' toggle to the 'on' state.
4. Close the system menu.
5. Touch a text field.

What happens: The VK appears when I give a textfield focus with touch, and this is what I expect would happen.

Similarly, if I:

1. Enter touchview and plug in an external keyboard.
2. Open the IME detailed view.
3. Set the 'on screen keyboard' toggle to the 'off' state.
4. Close the system menu.
5. Touch a text field.

I do *not* see the virtual keyboard appear, which is what I would expect since the toggle was set to off.

I checked on 57.0.2926.0 and 56.0.2924.3, i see the behavior as in #6 , which is the expected behavior. 

Hence closing the issue