Re: [csswg-drafts] [css-sizing] Adding a 'size' shorthand for 'width'/'height' (#820)

The CSS Working Group just discussed `Adding a 'size' shorthand for 'width'/'height'`, and agreed to the following:

* `RESOLVED: We are redefining the size property in @page to be called page-size. Also defining that size in the page context parses into page-size. The size property is a shorthand for width and height`

<details><summary>The full IRC log of that discussion</summary>
&lt;dael> Topic: Adding a 'size' shorthand for 'width'/'height'<br>
&lt;dael> github: https://github.com/w3c/csswg-drafts/issues/820<br>
&lt;dael> TabAtkins: discussed in past. Useful b/c size often set together. @page rule has a size declaration and we can't collide names.<br>
&lt;dael> TabAtkins: fantasai had a great suggestion to unblock. Rename @page declaration to page-size. Define @page has a parse time alias of size turning into page-size and that frees up size.<br>
&lt;dael> TabAtkins: Any existing pages using size will work. Anyone using CSSOM to page @page will see a page-size property. I suspect that's almost 0 since @page is only useful in printing. Printing doesn't have much JS support. Almost no possible breakage and this will let us do the size thing we've wanted to do for at least a decade.<br>
&lt;dael> TabAtkins: Clever way to get what we want.<br>
&lt;dael> florian: I think you're slightly overstating lack of JS support, but I agree with the argument<br>
&lt;dael> Rossen_: It's a cool proposal. I'm in favor. Other opinions?<br>
&lt;dael> dauwhe: I'll try and contact Prince about this<br>
&lt;dael> dauwhe: They're a PDF formatter that uses @page and supports JS<br>
&lt;dael> Rossen_: Should we wait?<br>
&lt;dael> dauwhe: No, go ahead<br>
&lt;dael> Rossen_: Thanks for the reach out<br>
&lt;dael> florian: Since this is new aliasing should we be explicit about how it can be used<br>
&lt;dael> fantasai: It's defined at parse time and you never see the other name.<br>
&lt;dael> florian: Of CSS file?<br>
&lt;dael> AmeliaBR: Does become a question. If you use cssom method to pase string that's parsed that is also parse time. Need defined somewhere. Need to define it somewhere for explaining relationship of MS prefixed force-colors vs new force-color<br>
&lt;dael> florian: WE have general aliasing, but this alias is weird<br>
&lt;dael> TabAtkins: Normal is shorthanding based. Property then does show up in all contexts. THis would be not that. Does need clarification. Happy to work to see exactly what to clarify.<br>
&lt;dael> emilio: If can put width and height in @page this would be quirky because size means one thing in @page<br>
&lt;dael> emilio: Can set width and height in @page rule. Means size does something different in @page then everywhere else.<br>
&lt;dael> TabAtkins: That's why we can't overlap. b/c size is not a shorthand in @page<br>
&lt;dael> fantasai: Confusion from naming property anything other than 'size' is higher then size in @page not being width and height<br>
&lt;dael> florian: Dev tools should be warning about this. If page-width exists and you try and use size you should be warned.<br>
&lt;dael> TabAtkins: I don't think any browser respects @page size declaration<br>
&lt;dael> florian: Chrome does<br>
&lt;dael> TabAtkins: Okay. Cool. I think spec should clarify that it's page-size and it's required to do this parsing. And I'll file a bug on our dev tools that we should have a maybe use something else<br>
&lt;dael> Rossen_: Prop: Add size as a shorthand for width and height for everywhere by @page?<br>
&lt;dael> fantasai: Several things. 1) We are redefining the size property in @page to be called page-size.<br>
&lt;dael> Rossen_: Let's resolve there first<br>
&lt;dael> fantasai: Also defining that size in the page context parses into page-size<br>
&lt;dael> fantasai: Once that's resolved, then the size property is a shorthand for width and height<br>
&lt;dael> Rossen_: Objections to these three steps?<br>
&lt;dael> RESOLVED: We are redefining the size property in @page to be called page-size. Also defining that size in the page context parses into page-size. The size property is a shorthand for width and height<br>
&lt;AmeliaBR> (To clarify my earlier comment, the similarity to forced color was that any rule inside the `@media (-ms-high-contrast)`  would include an implicit `forced-color-adjust: none` declaration added at parse time. But doesn't look like that got included in the spec, it was just a suggestion of how MS could handle internally.)<br>
</details>


-- 
GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/820#issuecomment-542792268 using your GitHub account

Received on Wednesday, 16 October 2019 16:48:19 UTC