- From: Dael Jackson <daelcss@gmail.com>
- Date: Thu, 7 Jan 2016 05:32:18 -0500
- To: www-style@w3.org
Round Display
-------------
- RESOLVED: Have the computed value for polar-angle keywords
resolve to an angle
- Several people expressed support for position:
relative/absolute/fixed/sticky enabling the polar-*
properties, but at least one implementor needed more time to
investigate so the group will return to the topic, hopefully
next week.
- The group needed BradK to be in the meeting to discuss the
removal of polar-origin in favor of his center proposal.
Accepting the alternate proposal for snap points
------------------------------------------------
- MaRakow just came back from vacation today, but promised the
group something for next week's telecon.
Grid
----
- RESOLVED: Accept the new text for grid and multi-col changing
the floor to a required amount. The new text is: "For
the purpose of finding the number of auto-repeated
tracks, the UA must floor the track size to a UA-
specified value to avoid division by zero. It is
suggested that this floor be ''1px'' or less."
- The potential options for how to drop repeated grid tracks with
auto-fit came down to:
1. Drop all empty columns
2. Drop empty columns from either end
3. Drop empty columns from end end.
- Several people were against 3 because it removed the
symmetry of the property.
- The group didn't have a preference between 1 and 2, so
decided to stay with 1 since that's what's in the spec now.
- RESOLVED: Change the initial value of align-content to stretch
May F2F
-------
- There's still no final location for the May F2F.
===== FULL MINUTES BELOW =======
Agenda:
jihye: There is an unclear thing of polar-angle and
polar-angle-reverse value for transform function.
jihye: It needs to be decided if polar-angle value turns into an
angle or a keyword when determining the computed value of
transform.
jihye: In the last telecon fantasai said if the keyword remains as
a keyword I can't animate between it and another angle
value. For example animating between rotate polar-angle and
another rotate is impossible.
<jihye> If the keyword value remains as a keyword, you can't
animate between it and another angle value. For example,
animating between rotate: polar-angle and rotate: 0 isn't
possible. However, when polar-angle property animates, the
changes in it affect to the rotation function with the
keyword value. If the keyword value turns into an angle,
you can animate between it and a different angle. Thus you
can animate between rotate: polar-angle and rotate: 0 or
betwe[CUT]
jihye: If polar angle property animates, the keyword will not
track the changes in polar-angle property. Did I understand
right?
TabAtkins: I think so.
Florian: That's what we said, but I'm not clear why it wouldn't
track. If it computes to an angle and polar-angle is
changing, why is it not animating?
jihye: I was also curious about that. I wrote this (below) in the
mailing list with some questions.
<jihye>
astearns: This is a hold over from last year's meeting.
astearns: Is it TabAtkins or fantasai that wants this?
TabAtkins: This was applying a min-size to auto-repeat. Does
anything need to be decided?
Rossen: I don't recall us resolving.
TabAtkins: Okay. auto-repeat has a space to fill, you give it a
track list, and it tries to fill. If it's 0px you can
end up with infinite.
TabAtkins: So we now have a UA defined minimum, we recommend 1px
because it's nice and small. And we need to apply that
to multi-col because it has the same problem.
TabAtkins: Unless there's an alternative, we can resolve on this.
Rossen: I'm okay with the change. My only ask is we make 1px
clearly that in the spec so it's easier to text instead of
it being suggested and everyone does their thing.
TabAtkins: Okay.
RESOLVED: Accept the new text for grid and multi-col changing the
floor to a required amount. The new text is: "For the
purpose of finding the number of auto-repeated tracks,
the UA must floor the track size to a UA-specified value
to avoid division by zero. It is suggested that this
floor be ''1px'' or less."
fantasai: The current minimum in Mozilla is 1/60 px.
Rossen: That's why I brought it up.
astearns: Who will change multicol?
Florian: I will.
TabAtkins: I will.
Florian: I'll leave it to TabAtkins
Dropping empty repeated tracks
------------------------------
<astearns> http://threesjs.com/ imagine these are using
repeat for creating the tracks
astearns: gregwhitworth posted a link to a game grid, but I'm not
sure you would use a repeat there. I assume it's a 4x4
grid.
fantasai: It wouldn't be auto repeating.
Rossen: Is the dropping specify that it's an empty column across
all rows?
fantasai: Yes. You can't drop a track if there's stuff in it.
<fantasai> spec link -
TabAtkins: Right now if you have a grid that's smaller than the
container it defaults to start, start. Flexbox defaults
to stretch. Javier in Chrome thinks this inconsistency
odd and would like both to have stretch.
TabAtkins: Stretch only effects auto-sides grid tracks, so that's
the only change.
fantasai: And if you don't have a container fixed to be larger you
won't have an effect. So auto-size grid containers don't
have an effect.
TabAtkins: So this effects grid containers set larger than grid
inside and the grid has at least one auto-track
fantasai: I'm in favor of consistency. In the past there wasn't a
way to handle stretch in the past, but there is now.
<astearns> +1 for consistency
TabAtkins: The original decision wasn't intentional exclude, it
was because we couldn't. Does anyone object to the
consistency change?
Rossen: Sounds okay.
RESOLVED: Change the initial value of align-content to stretch
May F2F
=======
astearns: That's the end of the agenda.
Rossen: Did we ever settle the May F2F location?
astearns: No.
Rossen: I remember we decided west coast, but nothing more.
plinss: I have an inquiry to see if I can host, but no reply.
Rossen: We should solve that by end of month.
Florian: So we said west coast, even just CA. Is it HP or someone
else, or just HP possible to host?
Rossen: Did we ever settle on CA or all of west coast?
Florian: I think so, but may be wrong.
Rossen: So I'll let the people from southern west coast explore
options.
astearns: So hopefully we'll hear something soon.
Rossen: One more quick item. I e-mailed the list from TPAC about
specs we agreed to update. Please give that a look and
update items as you find time
astearns: And if we don't have an update soon, we'll bug people.
astearns: Thanks everyone for calling in, we'll talk next week.
Received on Thursday, 7 January 2016 10:33:17 UTC