- From: inoas via GitHub <sysbot+gh@w3.org>
- Date: Tue, 20 Dec 2016 16:05:45 +0000
- To: public-css-archive@w3.org
What would take precedence if width/height and `new-property` are set
and values are conflicting?
I'd argue something like this would make sense:
```css
.block {
height: 640px; /* change this through MQ */
width: 480px; /* change this through MQ */
}
img.some {
display: block;
width: 100%;
height: aspect(0.5); /* set's the height to half of the width
*/
height: auto(0.5); /* set's the height to half of the width
*/
height: auto-aspect(0.5); /* set's the height to half of the width
*/
height: auto-ratio(0.5); /* set's the height to half of the width
*/
height: auto-ratio(golden); /* set's the height to golden cut */
height: auto-ratio(calc(9/16)); /* set's the height to 16:9 */
}
```
--
GitHub Notification of comment by inoas
Please view or discuss this issue at
https://github.com/w3c/csswg-drafts/issues/820#issuecomment-268282394
using your GitHub account
Received on Tuesday, 20 December 2016 16:05:51 UTC