W3C home > Mailing lists > Public > public-css-archive@w3.org > December 2020

Re: [csswg-drafts] [css-values-4] Clarify how and when the initial containing block and visual viewport may deviate (#5777)

From: mind-bending-forks via GitHub <sysbot+gh@w3.org>
Date: Sat, 12 Dec 2020 01:14:10 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-743572191-1607735649-sysbot+gh@w3.org>
> > * You say it _doesn't_ ever change size in response to pinch-zoom.
> 
> It depends on your frame of reference :)
> 
> Pinch-zooming changes the ratio of CSS pixels to screen pixels. The ICB size remains constant _in CSS pixels_, and varies _in screen pixels_, as you pinch-zoom.

Thanks @theres-waldo. Wow! I didn't realise I'd need to be Einstein to get my head around positioning a few rectangles 😀 That's a lot of degrees of freedom for my brain to cope with, so please give me some time to digest that.

> > * On Chrome for Android, 100% corresponds to the the initial height of the viewport _with the address bar_. Here however, the address bar persists and cannot be hidden. So, this works in the sense that the content fills the available viewport and the scrolling seems to work as it should too. Pinch-zoom works as you would expect.
> 
> This is the behaviour I had in mind for `100%`. To the extent that Firefox doesn't behave like this, those are bugs we should fix in Firefox.
> 
> The question is: are you happy with this behaviour as a page author?

Regarding Chrome's behaviour, I'll have bit more of a play to be sure, but for this specific holy-grail-type example, yes, it appears I am happy! It would be nicer if there was a way to trigger the address bar to hide and to consume the whole space potentially available as is normally possible, but this is only a minor inconvenience that I'm not that bothered by. Far more important is the fact that the layout (by which I mean header and footer positioning in relation to viewport) and behaviour (scroll) are both consistent across desktop and mobile with no truncation of content. So, while this doesn't necessarily fix the issues with `vh`, it's a good workaround for this example as far as I am concerned. I'd be interested to know what Safari on iOS does with this.

-- 
GitHub Notification of comment by mind-bending-forks
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/5777#issuecomment-743572191 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Saturday, 12 December 2020 01:14:11 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 06:42:24 UTC