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

Re: [csswg-drafts] [css-values-4] Add vhc value (#4329)

From: mind-bending-forks via GitHub <sysbot+gh@w3.org>
Date: Fri, 20 Nov 2020 17:50:07 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-731313467-1605894606-sysbot+gh@w3.org>
Thanks @frehner.

> in other words, perhaps this proposal could help you in the meantime (if it's accepted/implemented).

I appreciate your efforts. Unfortunately this proposal won't help our particular case.

I'm new here and not familiar with the CSS spec process. Please can you point me to the full specification of exactly what this proposal is, so that I am not talking at cross purposes? Is it literally just what is said in the Proposal section of https://github.com/w3c/csswg-drafts/issues/4329#issue-495372962, that is, to introduce a new unit, `vhc` that is based on the minimum possible viewport size, or is it more than that? Earlier comments in the thread give the distinct impression that `vh` itself was being changed or being considered for change too.

Also, we initially raised an issue about the breakage in Firefox for Android, and were told that it would be addressed by [this issue](https://bugzilla.mozilla.org/show_bug.cgi?id=1663000), but then that issue was subsequently closed without fixing the breakage. When we commented on the closure, we were pointed to [a document](https://github.com/bokand/URLBarSizing) that indicates that Safari, Firefox and Chrome mobile browsers are now all taking the definition of `vh` to be "relative to the largest possible viewable area" (rather than as per the CSS spec). When we complained about that we were told:

>  If you want to change the `vh` unit behavior, you should open a spec issue in https://github.com/w3c/csswg-drafts instead.

which led us to believe that `vh` had or was *already* being redefined in the standard to be "relative to the largest possible viewable area" and that we would need to open a spec issue if we wanted to change it back. We were also told:

> There is an ongoing discussion to change the spec description about `vh` units and introduce a new CSS unit which is not including dynamic toolbar height, it's https://github.com/w3c/csswg-drafts/issues/4329

Again, we read this as two things: a) change the spec description about `vh` and b) introduce a new CSS unit.

We were also asked to file new issues in against Firefox for the problems that had not been addressed, one of which was the specific breakage I have been referring to. That was then marked as WONT FIX though with a link to this thread.

So, we understood (perhaps misunderstood) that this thread and associated proposed changes to the CSS spec were being:

- used as a *justification* for marking the current breakage as WONT FIX in Firefox (else why mark as WONT FIX) and
- that the `vh` unit was being suggested for modification here too... (with earlier comments in the thread talking about how `vh` can be changed to make it useful etc.)

So:

- If [the definition of `vh` in the spec](https://www.w3.org/TR/css-values-3/#viewport-relative-lengths) is not actually being changed, then I'm not sure that I need to file a proposal here. If it is agreed that `vh` is intended to be relative to the "visible" viewport size, then mobile browsers are currently not respecting that. It would seem that I need to file new issues on Firefox, Safari and Android requesting that they change the way they work to be compatible with the spec. and so my proposal needs to be sent to them (in triplicate?) instead.
- If the definition of `vh` *is* being considered for change within the CSS spec (for example, to mean "relative to the largest possible viewable area"), either here or in some other proposal, then please can someone point me to that, so that I can comment there?

Thanks.

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


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 20 November 2020 17:50:09 UTC

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