-
Notifications
You must be signed in to change notification settings - Fork 669
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[css-values] Logical equivalents for vw/vh units #113
Comments
I understand i for inline, and b for block, but what does s stand for? I assume the dimension would remain constant based on the writing mode of the root element only, and not vary relative to the element they are used in? |
|
Yeah, I'm fine with this. |
I'd drop the s, seems unnecessary. |
Btw, here's the www-style thread on this: https://lists.w3.org/Archives/Public/www-style/2015Sep/0253.html |
We resolved in the telcon to add |
Hm, unexpected complication: I'm defining them to take their direction from the root element, but what do we do when you evaluate them in a context without an element? Like, in MQ we define |
How about simply going with the initial value of the writing-mode property, which means in an MQ context, vi=vw and vb=vh? |
I suppose we should be using the same concept as (overflow-block), but that doesn't appear to actually be well-defined. |
I agree it should be the same for both, and I think that going with the initial value of the writing mode property (i.e. vertical is block, horizontal is inline) is the sane thing to do. |
Sounds good to me. |
Tab, this goes into L4. Which hasn't forked yet because we've got outstanding issues on L3 and can't republish CR. I've commented it out for now. |
I am soooo pumped for this. Ben waiting 20 some odd years to have something like vi and vb. Also, you rlly need to additionally add ci and cb which will stand for content inline (width) and content box (height) so you can dynamically scale your content to the size of its contents. To be honest, im just plain tired of all this crazy hacky, exhausting css whcih makes developers lives alot harder. If web browsers added in just theese 4 units, then CSS would be a billion times easier. Btw. I dont care about how hacky or inefficient the polyfill is for them, I just want em now! By the way, to avoid recursion, which theese units would make pretty easy, just make it so that the max recursion levels is like 1, or decideable by CSS like |
Add description for experimental API in polyfill/README.md
People may need to use viewport units in a writing-mode-aware way, so probably we should add logical equivalents for
vw
andvh
. They could be calledvis
andvbs
or something like that.The text was updated successfully, but these errors were encountered: