Re: [w3ctag/design-reviews] VirtualKeyboard API - show/hide policy (#498)

@rniwa could you please clarify your objection from [this comment](https://github.com/whatwg/html/issues/4876#issuecomment-585485280)?

I believe you are objecting to any deprecation or change in behavior for inputmode=none.  
This proposal doesn't suggest we deprecate inputmode=none.

I think the root of the confusion is that inputmode=none has some overlap with the VK APIs (but isn't a replacement) so at one point it was suggested that we could deprecate inputmode=none since we would have the more capable VK API.  @rniwa is saying that wouldn't be acceptable as inputmode=none has been promoted and is being used to dismiss the keyboard in some scenarios.

We therefore abandoned the idea of deprecating inputmode=none (in response to @rniwa's comment), but that doesn't mean we don't need the VK API.  The VirtualKeyboard interface and the virtualKeyboardPolicy attribute provides authors with the ability to:

1. Request that the keyboard be hidden
2. Request that the keyboard be shown
3. Handle an event for when the keyboard changes its visibility and adjust to the size and position of the keyboard
4. Prevent the visual viewport from being resized due to the appearance of the VK

inputmode=none only addresses the first of those capabilities and comes with side effects that are discussed in the same github issue ([see here](https://github.com/whatwg/html/issues/4876#issuecomment-541232517)).

Hope that helps clarify things.  I don't believe there is any conflict here.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/498#issuecomment-618675318