15:47:22 RRSAgent has joined #CSS 15:47:22 logging to http://www.w3.org/2009/05/13-CSS-irc 15:47:28 Zakim, this will be Style 15:47:28 ok, glazou; I see Style_CSS FP()12:00PM scheduled to start in 13 minutes 15:56:06 mollydotcom has joined #css 15:56:12 mollydotcom has left #css 15:56:51 Style_CSS FP()12:00PM has now started 15:56:58 + +1.858.216.aaaa 15:57:20 zakim, +1.858.216 is me 15:57:20 +plinss; got it 15:57:54 +glazou 16:01:46 CesarAcebal has joined #css 16:03:13 +[Microsoft] 16:03:28 +Bert 16:03:33 sylvaing has joined #css 16:03:42 Zakim, [Microsoft] has sylvaing 16:03:44 +sylvaing; got it 16:05:03 +David_Baron 16:05:40 +??P21 16:06:13 fantasai: you join the call? 16:07:08 Scribe: Bert 16:07:08 +SteveZ 16:07:14 ScribeNick: Bert 16:07:24 Topic: 2.1 issues 16:07:37 http://wiki.csswg.org/spec/css2.1#issue-117 16:08:12 +??P29 16:08:24 alexmog has joined #css 16:09:00 zakim, ??P21 is CesarAcebal 16:09:00 +CesarAcebal; got it 16:09:12 zakim, ??P29 is fantasai 16:09:12 +fantasai; got it 16:10:03 http://lists.w3.org/Archives/Public/www-style/2009May/0067.html 16:10:10 David baron sent some replies. 16:10:26 szilles has joined #css 16:10:54 David: We might want to define issue 4, indeed. We would need test cases. 16:11:13 issue 4a 16:11:18 ? 16:11:54 David: Specifically 4a. 16:12:32 David: I already pointed out it was udnefiend 10 years ago and the group decided to leave it 5 years ago. But we might change our mind. 16:13:00 Bert: Defined at some point, yes, but needed for 2.1? 16:13:15 David: Maybe not necessary, but we won't get interoperability. 16:13:53 Arron has joined #CSS 16:14:09 Daniel: So we confirm that we leave it undefined? 16:15:35 (Discussion about what 2004 decision meant...) 16:16:24 +??P0 16:16:37 David explains the "root" in that decision. 16:16:37 Zakim, who is here? 16:16:37 On the phone I see plinss, glazou, [Microsoft], Bert, David_Baron, CesarAcebal, SteveZ, fantasai, ??P0 16:16:39 [Microsoft] has sylvaing 16:16:40 On IRC I see Arron, szilles, alexmog, sylvaing, CesarAcebal, RRSAgent, Zakim, glazou, arronei, dbaron, Lachy, krijn, jdaggett, karl, plinss, Hixie, fantasai, Bert, trackbot 16:16:48 David: We don't have good terminology. 16:16:54 zakim, ??P0 is alexmog 16:16:54 +alexmog; got it 16:17:26 David: An element inside a top-aligned is not a root and is not considered for the alignment of that root. 16:18:11 ScribeNick: fantasai 16:18:13 Steve: For XSL I said top was considered first and than the bottom-aligned elements would align to what was the resulting bottom after the rest was aligned. 16:18:22 s/than/then/ 16:18:29 Steve: XSL, you align all the things that are neither top nor bottom-aligned 16:18:41 Steve: Then you align against top, then bottom 16:19:02 s/against/things that are top/ 16:19:53 fantasai: Should we just copy XSL's definition? 16:20:12 David: We could use some test cases to see what browsers do 16:20:20 fantasai: Didn't Anton post a test case? 16:20:42 David: Some browsers might use always top, or always bottom, or the first thing, or the last thing. 16:20:51 ACTION Steve come up with wider set of testcases 16:20:51 Created ACTION-144 - Come up with wider set of testcases [on Steve Zilles - due 2009-05-20]. 16:21:28 Daniel: So we will return to 4a after analyzing testcases 16:21:41 Daniel: What abotu 4b? 16:21:49 David: We should come up with proposals for these 16:21:59 Daniel: That's ok, but who will come up with the proposals? 16:22:03 You align all the things that are neither top or bottom aligned; then next align the top items to the top of the first result and finally align the bottom aligned items to the bottom of the first two results 16:22:06 Steve: That should be either David or I 16:22:36 David: http://lists.w3.org/Archives/Public/www-style/2009May/0035.html 16:22:54 fantasai: I didn't have any proposals for this one, just filed the issue 16:24:17 http://lists.w3.org/Archives/Public/www-style/2009May/0084.html 16:24:19 fantasai: I folded Issue 4 and Issue 10 from that message into 117, they are all related and multiple bits might be solved by one proposal 16:24:39 Daniel: Ok, Steve will take care of this. Next issue 16:25:05 Topic: Background Shorthand for size 16:25:11 http://lists.w3.org/Archives/Public/www-style/2009May/0084.html 16:26:10 David: I don't like using slash as a delimiter when the item before it is optional 16:26:15 Daniel: Thoughts on this? 16:26:29 fantasai: Even the poster decided he didn't like this proposal, so I don't think we should adopt it. 16:26:34 http://lists.w3.org/Archives/Public/www-style/2009May/0030.html 16:26:38 Topic: pity thread 16:27:08 Daniel: Was there anything to extract from this email? 16:27:35 Bert: The first issue about the grammar, I made an error, it's my fault. 16:27:51 Bert: The others, he doesn't like the way we write it... and I don't like it either, the handling of errors is not very clear 16:27:58 Bert: I'm not sure we want to change that 16:28:21 Bert: The last one, the fonts one, we still have an open issue. We should wait for that before we decide anything new on fonts 16:28:29 Bert: I think John was going to come up with a proposal for that. 16:28:38 Daniel: So we have one error that you are going to fix, or have already fixed 16:28:49 Daniel: Two clarifications requested for the prose? 16:29:23 Bert: Number 2 in his mail is about ignoring until the end of the block. The way it's written now says "up to and including the end of the block", which is wrong 16:29:37 (we don't want to ignore the } ) 16:30:13 Bert: For number 3, I don't think we change anything there. I don't like the way it's written either, but I don't want to try to rewrite it. It's maybe not nicely written, but no real need to change. 16:30:14 "up to (but not including) the end of the block" 16:30:44 dbaron, that's not sufficient 16:30:58 dbaron, reread the paragraph, you need to rearrange some text for that to work 16:31:04 I can't find the paragraph 16:31:10 it's in Bert's mail 16:31:17 http://lists.w3.org/Archives/Public/www-style/2009May/0054.html 16:32:05 Search for "Maybe change from" 16:32:48 David: I think I prefer Bert's first proposal 16:33:05 fantasai: I would be ok with the first proposal if s/up to and including the next block/block/ 16:37:06 fantasai: but I guess that makes it ambiguous 16:37:45 it might be clearer if we say that it's the next semicolon not in a block 16:38:17 several prefer Bert's original proposal 16:38:27 fantasai: I can live with that if we add a comma before the second 'or' 16:38:40 RESOLVED: Bert's first proposal accepted with comma before second or 16:38:53 mine are not ready 16:39:00 not ready either 16:39:10 http://lists.w3.org/Archives/Public/www-style/2009May/0065.html 16:39:15 Nobody's ready with CSS2.1 issues 16:39:17 Next issue 16:39:33 Topic: REquest for new pseudos to Selectors spec 16:40:22 Daniel: I think it's too late in process to add these to css3-selectors 16:40:33 agreemeent 16:40:48 RESOLVED: Deferred to future specs 16:42:04 Daniel: Please make sure to book your hotels and flights 16:42:17 Daniel: And add topics to agenda http://wiki.csswg.org/planning/sophia-2009 16:44:25 Meeting closed 16:44:29 -David_Baron 16:44:31 -[Microsoft] 16:44:32 -plinss 16:44:33 -glazou 16:44:34 -SteveZ 16:44:35 -CesarAcebal 16:44:47 -Bert 16:45:01 rrsagent, make logs public 16:45:06 rrsagent, draft minutes 16:45:06 I have made the request to generate http://www.w3.org/2009/05/13-CSS-minutes.html Bert 16:45:34 -fantasai 16:46:22 trackbot, end meeting 16:46:22 Zakim, list attendees 16:46:22 As of this point the attendees have been +1.858.216.aaaa, plinss, glazou, Bert, sylvaing, David_Baron, SteveZ, CesarAcebal, fantasai, alexmog 16:46:23 RRSAgent, please draft minutes 16:46:23 I have made the request to generate http://www.w3.org/2009/05/13-CSS-minutes.html trackbot 16:46:24 RRSAgent, bye 16:46:24 I see no action items