- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Thu, 26 Sep 2024 19:02:37 +0000
- To: public-css-archive@w3.org
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: Accept what is in the draft` <details><summary>The full IRC log of that discussion</summary> <emilio> Or could<br> <ntim> lea, emilio: This illustrates florian's concerns: https://jsfiddle.net/5mb7efou/<br> <lea> astearns: fantasai and I thought we were pretty close to consensus, florian had a concern about the *current* behavior, and it seemed like everyone else was in agreement to do this?<br> <ntim> (open in Safari)<br> <kbabbitt> chrishtr: there are two modes supported that I think are common in mobile browsers for what to do about the interaction between fixpos elements in the page<br> <kbabbitt> ...layout viewport and visual viewport<br> <kbabbitt> ...two values are proposed, resize-visual and overlays-content<br> <kbabbitt> iank_: and resize-layout<br> <kbabbitt> chrishtr: it used to be that android chromium browsers only supported resize-layout, and webkit/safari only supported resize-visual<br> <kbabbitt> iank_: resize-visual or overlay-content, I forget which<br> <kbabbitt> chrishtr: compat concern from web developers<br> <kbabbitt> ...research found an app that is more app like and document like benefits from previous chrome/android behavior<br> <kbabbitt> ...other pages benefit more from the other value<br> <kbabbitt> ...difference often happens to do with when you open visual keyboard, does the visual viewport move up or not<br> <kbabbitt> ...sometimes you want it to move up, sometimes not<br> <kbabbitt> ...conclusion chrome came to is both values have value and we should support both<br> <kbabbitt> ...in the itnerest of iterop and because documents are more common than applications, default shoul dbe same as safari/webkit<br> <kbabbitt> ...thjat's what's shipped in Chrome so we have interop<br> <kbabbitt> ...implemented but not shipped in Firefox<br> <kbabbitt> ...meta tag to switch between modes to support app like user interfaces<br> <kbabbitt> ...instagram or twitter prefer the other mode because they have these little bars that want to be above virtual keyboard<br> <kbabbitt> ...they prefer the way android/chrome used to be<br> <kbabbitt> ...those browser support both more<br> <kbabbitt> ...proposal here is to standardize the meta tag<br> <kbabbitt> q?<br> <iank_> the three values are `resize-content`, `resize-visual` and `overlays-content`<br> <kbabbitt> ...meta tag is in editor's draft, is that editor's draft okay?<br> <dholbert> Firefox's switch to "resize-visual" (on Android) is shipping in version 132 (currently Nightly) as of https://bugzilla.mozilla.org/show_bug.cgi?id=1916002<br> <kbabbitt> iank_: we've also seen quite a lot of sites change to the resize content behavior<br> <bkardell_> carousel<br> <kbabbitt> emilio: there was another way of changing this behavior, right?<br> <kbabbitt> ...the virtual keyboard api?<br> <bkardell_> s/carousel/?<br> <kbabbitt> flackr: yes there's a virtual keyboard api to opt into overlay's content behaviior<br> <kbabbitt> ...not the most useful but ???<br> <kbabbitt> ...also not supported across all browsers<br> <kbabbitt> iank_: we've seen far more people use the interactive widgets meta tag<br> <kbabbitt> ...to opt into old chromium behavior<br> <kbabbitt> astearns: other questions?<br> <kbabbitt> Proposed: Accept what is in meta tag with the three values iank_ put in chat<br> <kbabbitt> astearns: objections?<br> <kbabbitt> RESOLVED: Accept what is in the draft<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-2377718287 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 26 September 2024 19:02:38 UTC