Re: [csswg-drafts] [css-viewport] Add a meta viewport parameter to control ICB layout behavior for interactive overlays (#7767)

The CSS Working Group just discussed `[css-viewport] Add a meta viewport parameter to control ICB layout behavior for interactive overlays`, and agreed to the following:

* `RESOLVED: Leave open, bring back in the upcoming F2F`

<details><summary>The full IRC log of that discussion</summary>
&lt;fantasai> emilio: Added to draft, but never got WG review<br>
&lt;fantasai> emilio: DIscussed adding meta viewport to control effect of keyboard on layout / visual viewport<br>
&lt;fantasai> emilio: I recall Jen presenting use cases for different things.<br>
&lt;fantasai> emilio: There are use cases for resizing either layout or visual viewport.<br>
&lt;fantasai> emilio: That changes things like fixedpos<br>
&lt;fantasai> emilio: This viewport meta key allows you to configure that behavior, as well as via JS virtual keyboard API.<br>
&lt;astearns> changes we are discussing: https://github.com/w3c/csswg-drafts/pull/7826/files<br>
&lt;fantasai> emilio: The tl;dr is, there are use cases for different behaviors<br>
&lt;fantasai> emilio: existing meta tag seems like the right place to configure this<br>
&lt;TabAtkins> Looks good to me, personally.<br>
&lt;fantasai> emilio: Are people OK with this? Gecko is implementing, Chromium may have shipped awhile ago, unsure about WebKit status<br>
&lt;fantasai> fantasai: This is the first I'm hearing about it. Recall discussing the problems, but don't recall resolving on adding this feature.<br>
&lt;fantasai> iank_: We made a switch to iOS behavior, but had compat issues, and needed to provide a toggle for the various behaviors.<br>
&lt;fantasai> emilio: Gecko and Blink used to resize the layout viewport for the keyboard<br>
&lt;fantasai> emilio: and iOS didn't<br>
&lt;fantasai> emilio: but sometimes could e.g. in webview<br>
&lt;fantasai> emilio: for Gecko to align with WebKit and Blink, we are also looking at implementing this<br>
&lt;fantasai> emilio: because use cases for other behavior<br>
&lt;fantasai> emilio: so this seems like reasonable place to opt into this<br>
&lt;fantasai> iank_: It's served us pretty well when we did this change.<br>
&lt;emilio> fantasai: I can't represent WebKit's position on this<br>
&lt;emilio> ... from my perspective it's not amazing that somebody edited it without bringing it up and now everybody is shipping it<br>
&lt;emilio> iank_: we did bring it up for discussion<br>
&lt;emilio> fantasai: interactive-widget doesn't show up in the mailing list<br>
&lt;emilio> fantasai: Just saying, let's avoid that kind of situation in the future<br>
&lt;emilio> astearns: it sounds like there was discussion in the PR<br>
&lt;emilio> ... which isn't great<br>
&lt;emilio> ... three different things we could do I guess<br>
&lt;emilio> ... leave issue open, bring it back in the f2f<br>
&lt;emilio> ... (2) accept PR, belatedly, open new issues if needed<br>
&lt;TabAtkins> +1 to 1<br>
&lt;emilio> ... (3) ack that we didn't follow process, rip it from the draft and opt in again<br>
&lt;emilio> chrishtr: +1 to 1<br>
&lt;chrishtr> https://github.com/WebKit/standards-positions/issues/65<br>
&lt;emilio> RESOLVED: Leave open, bring back in the upcoming F2F<br>
</details>


-- 
GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7767#issuecomment-2125261357 using your GitHub account


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

Received on Wednesday, 22 May 2024 16:38:55 UTC