[css-values-4] Add svh/svw, lvh/lvw, dvh/dvw length units (and *i/*b logical versions)
Categories
(Core :: CSS Parsing and Computation, enhancement, P3)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox101 | --- | fixed |
People
(Reporter: mozilla-apprentice, Assigned: hiro)
References
(Blocks 4 open bugs, )
Details
(Keywords: dev-doc-complete)
Attachments
(1 file, 4 external files)
|
13.96 KB,
patch
|
Details | Diff | Splinter Review |
A resolution was made for csswg-drafts/#4329.
[css-values-4] Add vhc value
- RESOLVED: Add a set of viewport units (vhc for ex.) that reflect the size of the layout viewport less all UA UI
Comment 1•6 years ago
|
||
(Note that the WG may still bikeshed the actual names to be used.)
For reference:
- Chromium Bug: https://bugs.chromium.org/p/chromium/issues/detail?id=1093055
- Webkit Bug: https://bugs.webkit.org/show_bug.cgi?id=219287
| Assignee | ||
Updated•5 years ago
|
| Assignee | ||
Updated•5 years ago
|
vhc has been replaced by the small (sv*), large (lv*) and dynamic (dv*) viewport units in CSS Values 4, following these two decisions: one, two. Will this bug be renamed and repurposed to cover it? If so, it should block https://bugzilla.mozilla.org/show_bug.cgi?id=1531237.
Comment 4•5 years ago
|
||
(In reply to Luke from comment #3)
vhc has been replaced by the small (sv*), large (lv*) and dynamic (dv*) viewport units in CSS Values 4, following these two decisions: one, two.
Thanks for noting that. This was ~expected, per comment 1 here.
Will this bug be renamed and repurposed to cover it?
Yes.
If so, it should block https://bugzilla.mozilla.org/show_bug.cgi?id=1531237.
Yup, makes sense.
| Assignee | ||
Comment 6•4 years ago
|
||
Updated•4 years ago
|
| Assignee | ||
Comment 7•4 years ago
|
||
Depends on D143252
| Assignee | ||
Comment 10•4 years ago
|
||
Depends on D143253
| Assignee | ||
Comment 11•4 years ago
|
||
Depends on D143259
Comment 12•4 years ago
|
||
This applies on top of the current version of D143252 and was sorta what I meant. Does something like this make sense to you? I don't think we need to care about the viewport vs dynamic viewport distinction in the computed style, in the sense that I expect elements using viewport units to be few, but if you think otherwise we can keep it.
The main thing I wanted is not having two different code paths to invalidate these, this makes the media query codepath call into InvalidateForViewportUnits(). What do you think about something like this?
Comment 13•4 years ago
|
||
Updated•4 years ago
|
Updated•4 years ago
|
Comment 14•4 years ago
|
||
Comment 16•4 years ago
|
||
| bugherder | ||
https://hg.mozilla.org/mozilla-central/rev/f0bf24a9a519
https://hg.mozilla.org/mozilla-central/rev/d9a19df80e22
https://hg.mozilla.org/mozilla-central/rev/32d002922d49
https://hg.mozilla.org/mozilla-central/rev/f7e13fe01ee4
Updated•4 years ago
|
Updated•4 years ago
|
| Assignee | ||
Updated•4 years ago
|
Updated•4 years ago
|
Comment 18•4 years ago
|
||
Documentation has been updated for new viewport sizes and new viewport-percentage units. Documentation has also been updated for the support of vi and vb units.
Doc: https://developer.mozilla.org/en-US/docs/Web/CSS/length#relative_length_units_based_on_viewport
Release note: https://developer.mozilla.org/en-US/docs/Mozilla/Firefox/Releases/101
Doc issue tracker (including issues pending review and approval): https://github.com/mdn/content/issues/15465
| Assignee | ||
Comment 19•4 years ago
|
||
I suppose bug 1779396 needs this new viewport units work.
Updated•3 years ago
|
Description
•