#498: VirtualKeyboard API - show/hide policy
Discussions
2020-04-20
Ken: 2 issues here, related but different. I think it would be better to split it up. Even 2 explainers. One of the APIs being explained is - if you have docked virtual keyboard, where is the keyboard? The other one is when the keyboard shows up you have more control over when it shows up and when it disappears... I think they are kind of distinct.
Dan: can you ask them to create a new issue?
Ken: I will create a new issue and copy the text. Creates #507
Ken: [on show/hide] MS has some good examples... examples from excel online... some other cases as well... when clicking from cell to cell...
Ken: there is a whatwg issue - they have
[discussing comments on the whatwg issue]
Alice: you've got to use the virtual keyboard policy to get that behavior.
Alice: It's not clear to me that it addresses the earlier comment about requiring a user action...
Sangwhan: if you just call focus with javascript you could force the virtual keyboard to show up...
Alice: i wonder if that's calling focus or using autofocus...
Ken: reads comment from oct 11
Dan: anne seems to be saying this has already been discussed, but their [whatwg] issue is still open...
Alice: person who filed our issue is did comment on their issue.
Dan: So should this have been filed as a dispute resolution?
Sangwhan: i can ask
2020-04-27
Ken: they are saying this is different [from the WHATWG issue]...
... asking for more comments.. not there yet...
Yves: let's let people try to get consensus first - in the end they may decide to do something different.
[set status and bumped]
2020-06-29
Ken: I think Bo's comments are pretty good. I'm OK with the idea. It's opt in. It seems usable.
Sangwhan: I'm not agreeing with the webkit position.
Ken: [giving some examples of when you want to have more control]
Sangwhan: I don't understand why they are against it.
Yves: when we say it looks OK it doesn't preclude it being worked on in a working group or that others can disagree.
Dan: yes.
[we agree that it looks OK
2020-10-12
Ken: they want to have a discussion at TPAC.
Dan: What venue?
Sanghwan: "Web apps editing" -
Dan: Should we wait or be a part of it?
Ken: let's let them come to conclusion.
Dan: Ok let's bump this issue until after TPAC.
2020-11-09
Ken: could we ask them to post a summary of their breakout session?
[bumped a week pending that feedback]
2020-11-16
Yves: there are new comments that seem to go in the right direction.
Ken: this sounds OK
Dan: OK enough to close the issue?
Ken: yeah I think so.
Dan: It's already set to proposed closed - let's close it in the plenary.
OpenedApr 10, 2020
Hello TAG!
I'm requesting a TAG review of VirtualKeyboard Policy API .
The Virtual Keyboard (VK) is the on-screen keyboard used for input in scenarios where a hardware keyboard may not be available. Unlike a hardware keyboard, a VK can adapt its shape to optimize for the expected type of input. Authors have control over the displayed shape of the VK through the inputmode attribute, but have limited control over when the VK is shown or hidden. We propose a new VirtualKeyboard interface that has APIs to provide authors with more control over when the VK is shown or hidden and also exposes the size of the VK so the page can reflow its content if part of it is occluded by the VK.
Further details:
We'd prefer the TAG provide feedback as (please delete all but the desired option):
🐛 open issues in our GitHub repo for each point of feedback