[csswg-drafts] [css-viewport] Can we avoid having two toggles for keyboard behaviour (interactive-widget and VirtualKeyboard.overlaysContent)? (#9476)

theres-waldo has just created a new issue for https://github.com/w3c/csswg-drafts:

== [css-viewport] Can we avoid having two toggles for keyboard behaviour (interactive-widget and VirtualKeyboard.overlaysContent)? ==
We have two different specs providing toggles for software keyboard behaviour:

 1. https://www.w3.org/TR/virtual-keyboard/#dom-virtualkeyboard-overlayscontent provides a two-way JS toggle in the form of `VirtualKeyboard.overlaysContent`
 2. https://drafts.csswg.org/css-viewport/#interactive-widget-section provides a three-way CSS toggle in the form of the `interactive-widget` key in the meta viewport tag

The CSS Viewport spec does have a [section](https://drafts.csswg.org/css-viewport/#interaction-with-virtualkeyboard-overlayscontent) discussing the interaction between these two toggles, which seems to make `overlaysContent=true` take precedence over `interactive-widget`... but this seems fairly confusing and error-prone.

Do we need to have two toggles in the first place? Can we agree on a single toggle, and deprecate/remove the other one from the relevant spec?

cc @emilio @hiikezoe

Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/9476 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Monday, 16 October 2023 22:34:07 UTC