- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Tue, 10 Apr 2018 12:27:42 +0000
- To: public-css-archive@w3.org
The Working Group just discussed `gutters`, and agreed to the following resolutions: * `RESOLVED: add an ar unit to the grid 2 spec for align content and justify content` <details><summary>The full IRC log of that discussion</summary> <astearns> topic: gutters<br> <astearns> github: https://github.com/w3c/csswg-drafts/issues/1116<br> <dael> fantasai: We resolved to add this to the first level of the WD. Just a request for people to let me know.<br> <dael> TabAtkins: Other then that I want a unit on these I think it looks great.<br> <dael> fantasai: unit proposed is ar unit for aspect ratio<br> <dael> astearns: Two options are a bare number or an ar unit<br> <dael> fantasai: I'm open to name suggestions<br> <dael> TabAtkins: I regret not putting unit on flex.<br> <dael> astearns: Could ar be used in other places?<br> <dael> TabAtkins: A generic aspect ratio<br> <dael> florian: It's mathematically unitless.<br> <dael> fantasai: It's a multiplier.<br> <dael> TabAtkins: Whatever the other thing results in multiply it.<br> <dael> florian: Does the unit thing play into if we want to ever use calc on it.<br> <dael> TabAtkins: Numbers tend to cause parsing issues. It causes issues on the flex things. I'd prefer not to keep that. This has a specific meaning so it should be tagged in a specific way. agnles are just numbers.<br> <dael> fantasai: They're not.<br> <dael> TabAtkins: They're radians which are just an ID.<br> <dael> fantasai: Somewhat releated discussion has been aspect ratio units needed, #1173<br> <ChrisL> how are radians an ID?<br> <dael> fantasai: There was a request for having an aspect ratio in the grid spec. A lot of the cases we want to have are covered by an aspect ratio property. Question was if there isn't an element can you asign the aspect ratio property.<br> <TabAtkins> ChrisL, Radian is (length of arc) / (length of radius), which is unitless<br> <ChrisL> an aspect ratio is (by definition) a ratio. It is a length divided by a length, and thus also unitless.<br> <dael> fantasai: You might decde you have a bunc hof fr columns and you want the rows to be 1:1. Once we add this if there's at least one element you can key off of you can auto-size the rest. If you don't put anything the auto row collapses to 0.<br> <dael> astearns: The only things in having that row were spanning it would be weird.<br> <TabAtkins> Yes, that's my point. We already associate units with "unitless" things, to give it an easily-interpreted meaning and help with parsing. THis is the same deal.<br> <dael> fantasai: One proposal was to have an ar unit in grid template columns that would represent the aspect ratio multiplied by the axis. QUestion was what if they are different sizes<br> <dael> fantasai: Proposal I had is 1ar is always 1fr in the other.<br> <dael> florian: You can't map to a colum 'cause you don't know which ot match.<br> <dael> fantasai: I'ts not clear what we need to do.<br> <dael> astearns: And a side discussion.<br> <dael> fantasai: A unit may be useful in this case.<br> <ChrisL> remember though that whenever we add units, it stops those things being used in custom properties, because we can't divide by united values<br> <dael> astearns: So do you want to resolve to add a ar unit?<br> <dael> TabAtkins: If we accept hte gap syntax I feel we should have a unit.<br> <dael> ChrisL: Remember when we add units you can't use them in custom properties. You can't devide by an ar.<br> <dael> TabAtkins: You can, ot works now.<br> <dael> astearns: Objections to adding an ar unit to the grid 2 spec for align content and justify content?<br> <TabAtkins> (I've been slow to add the functionality to calc(), but we resolved to do so a while back, and Typed OM allows it.)<br> <dael> RESOLVED: add an ar unit to the grid 2 spec for align content and justify content<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/1116#issuecomment-380080326 using your GitHub account
Received on Tuesday, 10 April 2018 12:27:45 UTC