Re: [csswg-drafts] [css-values-4] initial work on vhc unit proposal text. Resolves #4329 (#5108)

> I don't understand what you are mentioning about `vvh` as Visual Viewport Height being confusing.

![visual viewport vs vu](https://user-images.githubusercontent.com/175195/111428029-42c23500-86f7-11eb-8fab-85523acf5be3.jpg)

The draft is clarifying that 1 `vh` equals 1% of the height of the initial containing block with the user agent chrome at its smallest size. 1 `vhc` is defined as 1% of the height of the initial containing block with the user agent chrome at its largest size. 

Both values are defined in terms of the layout / fixed viewport.

Above there are three screenshots from a simulated iphone.

**Left: Chrome at smallest size**
On the left the viewport has user agent chrome at its smallest size.
Here the visual viewport height is equal to `100vh` (749px)

**Middle: Chrome at largest size**
In the middle the viewport has user agent chrome at its largest size.
Here the visual viewport height is equal to `100vhc` (635px)

**Right: With scale**
On the right the viewport has been scaled. (The viewport can be scaled either through pinch zooming, or by focusing on an input element.) The visual viewport height is now 437px, and not equal to `100vh` nor `100vhc`.


The height of the visual viewport will some times be equal `100vh` and other times be equal to `100vhc`. When scaled it will be a different value all together. Naming one of the units after the visual viewport is confusing, as the visual viewport changes and will equal either of the units at different states.

Maybe @bokand can weigh in here?

-- 
GitHub Notification of comment by johannesodland
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/pull/5108#issuecomment-800869937 using your GitHub account


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

Received on Wednesday, 17 March 2021 07:43:28 UTC