3 ms·
That makes it look like the "display" property will turn into a css shorthand for "inner" and "outer" display properties... is that the case?
by jpfed 10y ago
That makes it look like the "display" property will turn into a css shorthand for "inner" and "outer" display properties... is that the case?
- masklinn 10y agoIt is already that, it's been that pretty much all along, but for most of its history you couldn't set the inner and outer variants separately, you had to use "precomposed" values like inline-table. AFAIK you can't set the inner and outer display types via separate properties. Furthermore there are values which have more complex interactions/natures than just inner/outer e.g. "contents" (which removes the element's box but leaves the descendants — including pseudo-elements), "list-item" (which can be combined with any outer type but only the flow or flow-root inner types, and generates an internal pseudo-element), or the "internal values" which only make sense within wider display context (table and ruby).
- gsnedders 10y agoThere was, briefly, in Display Level 3 drafts, display-inline and display-outside properties, with display being a shorthand additionally supporting legacy values (like inline-block). It's now expected to be in Level 4[1]. [1]: https://lists.w3.org/Archives/Public/www-style/2014Sep/0399.html https://lists.w3.org/Archives/Public/www-style/2014Sep/0399....