15:32:37 RRSAgent has joined #css 15:32:37 logging to http://www.w3.org/2012/06/27-css-irc 15:32:43 Zakim, this will be Style 15:32:43 ok, glazou; I see Style_CSS FP()12:00PM scheduled to start in 28 minutes 15:32:49 RRSAgent, make logs public 15:49:20 dbaron has joined #css 15:51:58 oyvind has joined #css 15:54:00 tpod has joined #css 15:56:54 dstorey has joined #css 15:57:11 Style_CSS FP()12:00PM has now started 15:57:11 rbetts has joined #css 15:57:17 florian has joined #css 15:57:17 +??P7 15:57:23 Zakim, ??P7 is me 15:57:23 +glazou; got it 15:57:41 +??P8 15:57:50 +??P10 15:57:56 zakim, ??p8 is glenn 15:57:56 +glenn; got it 15:57:57 Zakim, I am ??P10 15:57:57 +florian; got it 15:58:03 -glazou 15:58:13 antonp has joined #css 15:58:14 + +1.604.312.aaaa 15:58:27 +aaaa 15:58:29 +??P7 15:58:31 bradk has joined #css 15:58:35 Zakim, ??P7 is me 15:58:35 +glazou; got it 15:58:58 Zakim, aaaa is me 15:58:58 +rbetts; got it 15:59:08 arron has joined #css 15:59:18 + +1.206.390.aabb 15:59:24 zakim, aabb is me 15:59:24 +stearns; got it 15:59:35 +sylvaing 15:59:38 +??P29 15:59:42 +??P18 15:59:48 zakim, ??p18 is me 15:59:48 +koji; got it 15:59:50 +bradk 16:00:03 +??P27 16:00:18 smfr has joined #css 16:00:25 +plinss 16:00:44 zakim +??P27 is me 16:00:45 JohnJansen has joined #css 16:00:45 +[Microsoft] 16:00:50 + +93192aacc 16:00:58 Zakim, Microsoft has JohnJansen 16:00:58 +JohnJansen; got it 16:01:03 Zakim, aacc is me 16:01:03 +antonp; got it 16:01:07 can i really not type the code before the dude stops talking? 16:01:17 doesn't seem like it 16:01:19 seems that way :-/ 16:01:23 +fantasai 16:01:23 sucky 16:01:30 Zakim, who is noisy? 16:01:37 +smfr 16:01:41 glazou, listening for 11 seconds I heard sound from the following: rbetts (56%), ??P27 (12%), antonp (86%) 16:01:49 Zakim, mute antonp 16:01:49 antonp should now be muted 16:02:00 antonp: your phone is extremely noisy 16:02:10 should be better now 16:02:26 +SteveZ 16:02:52 Zakim, unmute antonp 16:02:53 antonp should no longer be muted 16:03:08 SteveZ has joined #css 16:03:09 zakim, ??P27 is me 16:03:09 +dstorey; got it 16:03:40 -glenn 16:04:04 Zakim, who is here? 16:04:04 On the phone I see florian, rbetts, glazou, stearns, sylvaing, ??P29, koji, bradk, dstorey, plinss, [Microsoft], antonp, fantasai, smfr, SteveZ 16:04:06 [Microsoft] has JohnJansen 16:04:06 On IRC I see SteveZ, JohnJansen, smfr, arron, bradk, antonp, florian, rbetts, dstorey, oyvind, dbaron, RRSAgent, Zakim, glazou, glenn, evanli, nimbu, jet, koji, miketaylr, 16:04:07 ... leaverou, drublic, Ms2ger, logbot, kennyluck, decadance, shepazu, florianr, isherman, arronei, stearns, Bert, Liam, ed, CSSWG_LogBot, dglazkov, heycam|away, macpherson, 16:04:11 ... gsnedders, TabAtkins, hober, trackbot, fantasai, Hixie, paul___irish, plinss, alexmog, shans, vhardy, sylvaing 16:04:14 + +1.619.846.aadd 16:04:34 +??P21 16:04:36 oops regrets wont be joining telecon. 16:04:49 zakim, ??p21 is me 16:04:49 +glenn; got it 16:05:18 i 16:05:32 s/i// 16:05:35 ScribeNick: florian 16:05:37 ScribeNick: florian 16:05:41 +dbaron 16:05:55 + +1.650.253.aaee 16:06:02 zakim, aaee is me 16:06:03 +TabAtkins; got it 16:06:14 - +1.619.846.aadd 16:06:18 glazou: I'll be away for 3 weeks, and peter also on the 11th of july 16:06:33 glazou: suggested replacement chair: Chris 16:06:46 Topic: Transforms, transitions, animations 16:06:57 + +1.619.846.aaff 16:07:03 Zakim, aaff is me 16:07:03 +hober; got it 16:07:12 ???: on transform, update from last week: 16:07:23 s/???/smfr/ 16:07:38 ???: ie and mozilla don't transform the background with attachement fixed 16:08:46 + +1.425.246.aagg 16:09:21 florian: opera is transforming the background, and scrolling it in in parallel with the element, not parallel with the page 16:09:26 alexmog__ has joined #css 16:09:32 ???: ie and mozilla do that too 16:09:38 s/???/smfr 16:10:03 zakim, last dude who called in is me 16:10:03 I don't understand 'last dude who called in is me', alexmog__ 16:10:19 Zakim, aagg is alexmog__ 16:10:19 +alexmog__; got it 16:10:41 dbaron: ie and moz draw the background as if there was no transform, and then transform 16:10:53 thx daniel 16:11:00 +??P8 16:11:17 ???: if you use the transform to flip things upside down, the background is going to scroll backward, which is weird 16:11:26 s/???/smfr 16:11:27 dbaron: they should put the background on an ancestor 16:11:53 miketayl_r has joined #css 16:12:00 dbaron: it is ok, as fixed background are really meant for the root elements 16:12:35 florianr: agree, we don't care too much about what happens on non root elements 16:13:03 smfr: should we define it then 16:13:47 florian: not expected use case, but will probably be used, so we should define 16:14:12 dbaron: we should define, to avoid people depending on a behavior we wouldn't want 16:15:06 smfr: I would prefer to define it in a way that means you don't have to repaint the background when you scroll the page 16:15:23 dbaron, tab: sounds acceptable 16:15:37 glazou: anything else? 16:15:59 ACTION smfr write a proposal about fixed background and transforms 16:15:59 Created ACTION-481 - Write a proposal about fixed background and transforms [on Simon Fraser - due 2012-07-04]. 16:16:04 smfr: there is a little terminology issue, relating to containing blocs 16:16:41 sylvaing: animation, still 46 bugs 16:17:13 dbaron: no news on transitions, still have to go through the hard issues 16:17:55 glazou: next call is on us Independence day, can we have a call? 16:17:59 many: yes 16:18:02 Rossen has joined #css 16:18:08 +[Microsoft.a] 16:18:09 topic: flexbox 16:18:10 zakim, microsoft has me 16:18:10 +arronei; got it 16:18:13 http://wiki.csswg.org/topics/css3-flexbox-flexbox-replaced-children 16:18:43 -??P29 16:18:50 +[Microsoft.aa] 16:19:05 Zakim [Microsoft.aa] is me 16:19:11 Tab: still like proposal A 16:19:40 Zakim, [Microsoft.aa] is me 16:19:40 +Rossen; got it 16:20:46 -fantasai 16:21:13 florian: the reason I don't like A is that it's inconsistent 16:21:26 florian: what happens with regular elements differs from what happens to the special cased elements 16:21:27 +fantasai 16:21:42 florian: for buttons et al. you can't turn this behavior off 16:22:22 florian: either we need an opt out and B is fine, or we don't and D works 16:22:44 tab: D is not very flexible. 16:23:05 q+ 16:23:09 tab: B is more work that seems necessary 16:23:23 tab: A special-cases elements because these elements are special cases 16:23:42 tab: other document languages might have such cases but there is no good way to address this without defining new concepts 16:23:43 Zakim, ack smfr 16:23:43 I see no one on the speaker queue 16:24:04 smfr: could we make anonymous flex item containers for these elements? 16:24:27 tab: in some cases this wouldn't work well e.g. the anonymous container would be stretched but not its content 16:24:48 Zakim, who is on the phone? 16:24:48 On the phone I see florian, rbetts, glazou, stearns, sylvaing, koji, bradk, dstorey, plinss, [Microsoft], antonp, smfr, SteveZ, glenn (muted), dbaron, TabAtkins, hober, alexmog__, 16:24:51 ... ??P8, [Microsoft.a], Rossen, fantasai 16:24:51 [Microsoft] has arronei 16:24:51 glazou: many diverging opinions, it's time for a straw poll 16:24:53 http://wiki.csswg.org/topics/css3-flexbox-flexbox-replaced-children 16:25:37 florian: B or D (no objection to others) 16:25:39 rbetts: abstain 16:25:44 glazou: D 16:26:01 alan: not A 16:26:09 sylvaing: abstain 16:26:11 s/alan/stearns/ 16:26:17 koji: abstain 16:26:19 brad: D 16:26:22 dstorey: abstain 16:26:27 plinss: C, not A 16:26:42 rossen: c and then D, not A 16:26:45 arronei: not A 16:26:53 johnjan: C 16:27:04 antonp: prefer B or D, not C 16:27:09 smfr: abstain 16:27:09 zakim, Microsoft has JohnJansen 16:27:09 +JohnJansen; got it 16:27:22 abstain 16:27:22 szilles: abstain 16:27:28 dbaron: abstain 16:27:36 tab: A or D 16:27:39 hober: abstain 16:27:47 fantasai 16:27:56 not C 16:28:00 fantasai: not C 16:28:38 can eliminate A 16:30:01 glazou: let's straw poll C vs. D 16:30:12 florian: D 16:30:17 rbetts: D 16:30:20 glazou: D 16:30:34 alan: abstain 16:30:35 sylvaing: C 16:30:45 koji 16:30:48 abstain 16:30:51 brad: C 16:30:55 s/C/D 16:31:04 dstorey: D 16:31:19 brad: D 16:31:49 plinss: abstain 16:31:50 rossen: C 16:31:56 arronei: C 16:32:01 john: D 16:32:03 antonp: D 16:32:03 c as "charlie", d as "delta". 16:32:05 smfr: C 16:32:11 abstain 16:32:11 szilles: abstain 16:32:14 john was C not D 16:32:16 dbaron: D 16:32:18 tab: D 16:32:22 hober: abstain 16:32:25 alexmog: C 16:32:38 fantasai: C 16:32:41 alex: but ok with D 16:32:46 fantasai: D 16:34:01 fantasai: Several "not C"s, but no "not D"s 16:34:21 RESOLVED: Proposal D for handling of replaced elements as flexbox items 16:34:50 http://wiki.csswg.org/topics/overflow-formatting-context 16:35:12 Topic: Formatting Contexts (2.1) 16:35:18 antonp: Just waiting for review from a couple people on this 16:35:29 antonp: haven't heard back from dbaron 16:35:42 florian: resolution was accept unless dbaron says no 16:36:19 dbaron: you should just go ahead without me 16:36:22 antonp: Rossen replied on the list, haven't heard back after response 16:36:59 Topic: vmax 16:37:00 http://lists.w3.org/Archives/Public/www-style/2012May/1198.html 16:38:03 fantasai: We have vmin, request was to add vmax 16:38:26 tantek has joined #css 16:38:52 ?: Are their use cases? 16:39:01 tab: person posting didn't give a precise example, but did say there were some 16:39:08 s/?/hober/ 16:39:11 florian: if you think of it as cover vs contain, makes sense 16:39:16 tab: Once you have vmin, vmax is trivial 16:39:40 RESOLVED: Add vmax 16:40:32 http://lists.w3.org/Archives/Public/www-style/2012Jun/0446.html 16:40:39 s/german/benjamin ... 16:42:46 florian: calc() inside calc() makes sense to me 16:43:00 if we are fossils, we need chalk() 16:43:13 florian: unless we want to open debate of whether calc exists at all and just use bare parens 16:43:26 glazou: Are there any objections to calc() inside calc()? 16:43:29 silence 16:43:34 RESOLVED: calc inside calc allowed 16:44:30 fantasai: the other issue that's open is precision 16:45:04 http://dev.w3.org/csswg/css3-values/issues-lc-2012#issue-25 16:45:06 krijnh has joined #css 16:46:56 fantasai ... 16:48:18 Topic: CSS3 Background 16:48:25 fantasai: wanted to update the CR, dbaron had an issue on animations line 16:48:39 fantasai: seems like a lot of mostly redundant info, was wondering if we can keep that in the transitions spec 16:48:46 dbaron: yeah, can probably keep in transitions spec 16:49:01 florian: There are a number of background properties that take a list 16:49:13 florian: if there are fewer than images, then repeat the list 16:49:24 florian: computed value is as specified 16:49:31 hober + sylvaing +++ 16:49:33 florian: ... trigger a transition 16:49:50 florian: does adding to the list trigger a transition, even if no layers are added? 16:49:58 Tab: It would be a null transition 16:50:02 florian: would send out events, though 16:50:34 florian: Seems more natural for computed value to reflect the value we're using in theory 16:50:42 fantasai: would you truncate the specified value if it's too long then? 16:50:44 florian: yes? 16:50:53 nimbu: don't tempt him :) 16:50:55 dbaron: i think this is too late to change it 16:51:04 dbaron: we do this computed value line across 3-4 specs now 16:51:07 dbaron: too late to change them 16:51:46 fantasai: if no one has other changes to make, suggest publishing update to CR 16:51:50 florian: Another question... 16:52:09 florian: background-position, syntax where you say 'right 10px' is equivalent to 'calc(100%-10px)' 16:52:16 florian: probably too late to change that though 16:52:37 florian: Mozilla shows that in its computed value 16:52:41 fantasai: that's incorrect per spec... 16:52:55 glazou: :)) 16:52:55 RESOLVED: publish updated CR of CSS3 Backgrounds 16:53:07 Topic: 2.1 16:53:12 Rossen: Just read anton's reply 16:53:28 Rossen: My issues with the proposal was the fact that when you read 2.1 sections 9.2.1 16:53:43 http://www.w3.org/TR/CSS21/visuren.html#inline-boxes 16:54:04 Rossen: talks about when an inline level box is created 16:54:15 http://www.w3.org/TR/CSS21/visuren.html#inline-formatting 16:54:17 rossen: inline-table and inline-block generate inline-level boxes, which participate in inline formatting context 16:54:41 rossen: we have 9.... that talks about inline formatting context, but doesn't say what establishes it 16:54:54 rossen: neither 2.9.4.2 nor 9.2.2 16:55:10 rossen: Because of this I can easily deduce that an inline formatting context can be created by an inline non-replaced element 16:55:12 s/2.9.4.2/9.4.2 16:55:19 rossen: issues I raised would become a problem 16:55:33 rossen: ok with proposed definitions, as long as we take an action to clarific exactly what you said 16:55:41 rossen: and state when an inline formatting context is created 16:56:56 rossen: want to be assured that an inline elements don't establish an inline formatting context 16:57:25 fantasai: "An inline box is one that is both inline-level and whose contents participate in its containing inline formatting context." (9.2.2) 16:57:51 rossen: if we add to beginning of inline formatting context "inline formatting context is established by ...." then there will be no ambiguity 16:58:17 antonp: "A block container box either contains only block-level boxes or establishes an inline formatting context and thus contains only inline-level boxes." 16:58:36 antonp: before nothing said what establishes an inline formatting contexts 16:58:53 antonp: I understand your concern that it's not clear that an inline box does /not/ establish an IFC 16:59:04 rossen: if that's clarified, then all my concerns are invalid 16:59:20 rossen: so if we're ok with adding this clarification, then I don't have a problem 16:59:41 rossen: there's a behavior difference... 16:59:47 rossen: it appears that Gecko has overflow for table 17:00:04 antonp: according to the email, behavior is 50/50 17:00:09 antonp: among 4 key implementations 17:00:55 antonp: øyvind sent an email that there's a difference as to whether overflow is applied to table box or table wrapper box 17:01:14 fantasai: so do we accept the edits or no? 17:01:17 rossen: I'm ok with this 17:01:24 rossen: concerned about change of behavior in implementations 17:01:30 antonp: Isn't it the case that IE won't have to change? 17:01:40 rossen: IE as of 9 and 10 will have that change 17:01:52 gtg 17:01:53 rossen: I guess we didn't see any records that this is breaking anything when we changed it 17:01:57 -smfr 17:02:20 florian: if we have implementations on either side, defining behavior of table is something we should do anyway 17:02:31 rossen: only question is, do we want scrollers on tables or no? 17:02:47 rossen: should we accept this, then? 17:02:56 rossen: anyone object to overflow on tables/ 17:03:03 rossen: curious about other implementers 17:03:06 -alexmog__ 17:03:12 dbaron and florian don't know 17:03:14 dbaron: I'd need to look into it. 17:03:31 tab: I know someone does overflow on 17:03:43 dbaron: I believe we stopped doing that, but I'm not sure 17:03:57 -[Microsoft] 17:04:09 rossen: easy enough to call it out explicitly as either yay or nay wrt overflow 17:04:17 rossen: my proposal is to go with majority of implementations 17:04:18 -dbaron 17:04:32 fantasai: so we have an action item to figure out what that is 17:04:57 glazou: ok, will deal with that http://test.csswg.org/shepherd/testcase/overflow-applies-to-013/ 17:05:10 later 17:05:11 -hober 17:05:12 Meeting closed. 17:05:12 -rbetts 17:05:14 -glazou 17:05:16 antonp has left #css 17:05:16 -koji 17:05:17 -SteveZ 17:05:17 -plinss 17:05:19 -Rossen 17:05:19 -[Microsoft.a] 17:05:19 -glenn 17:05:20 -dstorey 17:05:21 -stearns 17:05:23 -antonp 17:05:25 -TabAtkins 17:05:27 -sylvaing 17:05:29 -bradk 17:05:31 florian has left #css 17:05:38 -fantasai 17:05:40 -??P8 17:05:45 -florian 17:05:46 Style_CSS FP()12:00PM has ended 17:05:46 Attendees were glazou, glenn, florian, +1.604.312.aaaa, rbetts, +1.206.390.aabb, stearns, sylvaing, koji, bradk, plinss, +93192aacc, JohnJansen, antonp, fantasai, smfr, SteveZ, 17:05:46 ... dstorey, +1.619.846.aadd, dbaron, +1.650.253.aaee, TabAtkins, +1.619.846.aaff, hober, +1.425.246.aagg, alexmog__, [Microsoft], arronei, Rossen 17:06:16 TabAtkins: so... plan for tomorrow, finish css3-values, and work on flexbox? 17:06:30 fantasai: Yup. 17:07:21 arronei: you wrote a testcase already 17:08:43 tantek has joined #css 17:08:43 Yay, test cases 17:10:42 fantasai: Also we can talk a little about positioning, since you have Opinions on it and we have someone wanting to implement. 17:15:16 TabAtkins: I don't have Opinions on it, I just have no idea what it's trying to do 17:20:20 evanli has left #css 17:22:54 fantasai: That counts. 17:23:05 As an opinion? no 17:23:50 shepazu: Is Fullscreen getting published tomorrow? 17:24:22 working on it right now, actually 17:24:30 it should be published tomorrow 17:27:55 cool 17:33:36 oyvind has left #css 17:34:39 dstorey has joined #css 17:43:39 shepazu, fantasai - that's great to hear - thanks! 17:48:20 fantasai: scratch that, it may have to wait until Tuesday 17:48:32 I'm trying to get our ducks in a row with ArtB 17:48:50 I'l try for tomorrow, but it may have to wait 18:04:48 jacobg has joined #css 18:48:28 tantek has joined #css 18:57:43 Zakim has left #css 19:02:02 dbaron has joined #css 19:40:01 nimbu has joined #css 19:53:18 drublic has joined #css 20:00:56 nimbu has joined #css 20:08:46 arno has joined #css 20:12:18 kennyluck has joined #css 20:15:22 drublic has joined #css 20:39:58 ksweeney has joined #css 20:43:57 ksweeney has left #css 20:59:07 nimbu has joined #css 21:28:10 nimbu has joined #css 21:50:34 nimbu: I can't speak for w3cmemes, but it will be in the minutes :) 21:58:41 fantasai nimbu: did w3cmemes miss a meme from this call? Two got posted... 22:00:35 nimbu has joined #css 22:10:41 tantek has joined #css 22:12:41 tantek_ has joined #css 23:00:09 drublic has joined #css 23:07:19 krijnh has joined #css 23:13:17 tantek has joined #css 23:31:20 myakura has joined #css 23:31:41 myakura has joined #css 23:31:49 jacobg has left #css 23:57:29 arno has joined #css