15:36:37 RRSAgent has joined #CSS 15:36:37 logging to http://www.w3.org/2010/05/26-CSS-irc 15:36:43 Zakim, this will be Style 15:36:43 ok, glazou; I see Style_CSS FP()12:00PM scheduled to start in 24 minutes 15:36:48 rrsagent, make logs public 15:46:20 sylvaing has joined #css 15:56:43 Style_CSS FP()12:00PM has now started 15:56:50 +plinss 15:57:33 +glazou 15:58:14 oyvind has joined #css 15:59:15 + +49.238.aaaa 15:59:27 Zakim, aaaa is CesarAcebal 15:59:28 +CesarAcebal; got it 15:59:50 +Bert 16:00:10 +[Microsoft] 16:00:14 +TabAtkins 16:00:18 zakim, microsoft is me 16:00:18 +arronei; got it 16:00:18 murakami has joined #css 16:00:27 smfr has joined #css 16:00:44 +sylvaing 16:02:16 +smfr 16:02:36 bradk has joined #css 16:03:46 +??P21 16:04:49 Zakim, ? is me 16:04:49 +fantasai; got it 16:05:01 why does my phone have to be difficult? 16:05:10 Zakim, who is noisy? 16:05:10 +bradk 16:05:22 glazou, listening for 10 seconds I heard sound from the following: CesarAcebal (24%), TabAtkins (14%), bradk (4%) 16:05:57 ScribeNick: TabAtkins 16:05:59 alexmog has joined #css 16:06:12 glazou: first item is about adding murakami-san as new editor for css3 lists. 16:06:13 +! 16:06:16 glazou: any objection? 16:06:50 RESOLVED: Murakami-san added as 3rd editor of css3 lists 16:07:05 thanks 16:07:09 glazou: First lets review the issues for everyone. 16:07:30 glazou: dbaron is not on the call yet. 16:07:34 glazou: elika? 16:07:42 fantasai: I haven't done any work on issues yet. 16:07:45 glazou: When will you? 16:07:53 fantasai: Early june, as I reported last week. 16:07:58 glazou: Sylvain? 16:08:23 sylvaing: Anton got back to me; we're basically done, but he's asking me to reconsider something. I need to read through the whole thread which is very time-consuming. 16:08:35 glazou: You're confident you can have a proposal for the issue by next week? 16:08:37 sylvaing: Yes. 16:08:49 glazou: Bert? 16:09:03 Bert: I did 119 just now. 16:09:08 + +47.23.69.aabb 16:09:19 Bert: 120 and 122 are being added. I don't think they need further discussion, though. 16:09:26 Zakim, aabb is howcome 16:09:27 +howcome; got it 16:09:36 glazou: arron? 16:09:52 arronei: Created test cases, but had some problems with uploading them last night; access was blocked for some reason. 16:10:05 s/they need/any of the others need/ 16:10:24 s/122/121/ 16:11:05 glazou: tab? 16:11:26 that typing is really loud. Not that I'm complaining about a person other than me scribing. 16:11:29 http://wiki.csswg.org/spec/css2.1#issue-138 16:11:34 TabAtkins: I'm still discussing issue 161 with boris, but I think I'm finally to a point where he's happy with the wording (even if not with the proposal itself). I should have it wrapped up this week. 16:14:06 glazou: issue 138 16:14:36 TabAtkins: I think that what fantasai explained as what it's "trying to say" is correct, but as boris says, we need to clarify it. 16:14:44 fantasai: What about abspos? 16:15:17 TabAtkins: Abspos elements act like blocks anyway, so that case should be less ambiguous. 16:15:21 So we want something like appending "If any floats are contained by the anonymous box, then those floats are shifted, too." 16:15:24 ? 16:15:25 glazou: Who volunteers to write a proposal? 16:15:33 TabAtkins: I'll try it out. 16:15:50 http://wiki.csswg.org/spec/css2.1#issue-139 16:15:51 ACTION Tab: Write proposal for issue 138 16:15:51 Created ACTION-232 - Write proposal for issue 138 [on Tab Atkins Jr. - due 2010-06-02]. 16:16:00 glazou: Next, issue 139, a grammar issue. 16:16:52 TabAtkins: Did we agree that that's a valid report? If so, then it's clearly an error - the escape character should never appear unescaped. 16:17:04 glazou: Any objections? 16:17:13 RESOLVED: Accept Yves's proposal for issue 139. 16:17:18 Bert: I'll make the edit. 16:17:25 http://wiki.csswg.org/spec/css2.1#issue-146 16:18:06 glazou: Issue 146. 16:18:14 glazou: Seems pretty simple. The marker box shouldn't be optional. 16:19:08 TabAtkins: Are we going to accept elika's wording? 16:19:20 fantasai: What do you mean? 16:19:43 glazou: It can be more explicit. It should say "no marker when list-style-type:none", etc. 16:19:53 fantasai: That's specified in the list section; this is the box generation section. 16:20:10 RESOLVED: Accept fantasai's proposal for issue 146. 16:20:35 http://wiki.csswg.org/spec/css2.1#issue-118 16:20:40 glazou: Now to the issues with no owner at all. First is 118. 16:22:46 Bert: It's imprecise. The glyphs aren't centered, the "em box" is. 16:23:25 TabAtkins: Yeah, not sure if we want to use the *term* "em box", but that's definitely the idea we're shooting for. 16:24:18 fantasai: What other term would we use? 16:25:14 TabAtkins: What about inline-blocks? 16:25:15 howcome has joined #css 16:25:28 Zakim, who is on the phone? 16:25:28 On the phone I see plinss, glazou, CesarAcebal, Bert, arronei, TabAtkins, sylvaing, smfr, fantasai, bradk, howcome 16:25:29 fantasai: This section is about text; you need the assumption of a font for this to make sense. 16:25:37 bradk: Some glyphs are taller than others. 16:25:48 TabAtkins: Yeah, but their em boxes are the same if their font-size is. 16:25:55 bradk: Do we define "em box" anywhere? 16:26:20 TabAtkins: No. It's a standard definition in fonts, but we should probably add a token definition of it. 16:26:39 glazou: So we more or less agree; who's going to write the proposal? 16:26:41 thought the leading was line-height-font-size and went on top/bottom of the content area where the glyphs go 16:27:17 Bert: I guess we need some text that says we assume each glyph is defined relative to an "em box". 16:27:31 fantasai: And we assume that the font-size is mapped to the em box. 16:27:48 or rather, the em box is mapped to the font size 16:28:07 ACTION Bert: Write proposal for issue 118. 16:28:07 Created ACTION-233 - Write proposal for issue 118. [on Bert Bos - due 2010-06-02]. 16:28:15 http://wiki.csswg.org/spec/css2.1#issue-122 16:28:25 glazou: Next is issue 122, related to fonts. 16:28:42 glazou: Reporter complains that the spec is redefining what "serif" and "sans serif" means. 16:28:48 glazou: And we have a proposal from dbaron to solve that. 16:29:33 TabAtkins: Agreed with dbaron's proposal - fonts already know if they're serif or whatever, and we can just have a weak description of what the terms mean. 16:29:52 http://somuchpun.com/?s=serif 16:30:03 RESOLVED: Accept dbaron's proposal to resolve issue 122. 16:30:51 ACTION Tab: Propose text for resolving issue 122. 16:30:51 Created ACTION-234 - Propose text for resolving issue 122. [on Tab Atkins Jr. - due 2010-06-02]. 16:30:53 http://wiki.csswg.org/spec/css2.1#issue-140 16:32:46 glazou: I think david's proposal makes sense - it's probably the only way to solve this problem. 16:33:48 TabAtkins: I don't have a deep enough understanding of the core grammar to know how good of a solution dbaron's proposal is, or what a better one is. 16:34:09 Bert: Another option, certainly, is to change the example that spawned the issue, and remove the braces from between the parens? 16:34:43 glazou: People could still write that sort of thing, correct? 16:35:02 Bert: Right, people can write things that can't be tokenized, and we just don't know what to do with them. 16:35:21 glazou: I don't think that's a good enough solution. 16:35:37 Bert: Do we want to define the meaning of every possible bytestream? I don't think that's needed. 16:35:44 glazou: I think it would be useful. ^_^ 16:35:53 glazou: I recommend waiting for dbaron to attend a call and get his input. 16:36:13 Bert: It's probably okay to allow braces inside parens, but I'm still a little bit afraid. 16:36:20 glazou: We'll revisit next week, and move on for now. 16:36:22 http://wiki.csswg.org/spec/css2.1#issue-142 16:37:43 TabAtkins: We do need a definition of what the "ancestor box" is, because Boris and I disagreed on that while discussing my abspos-in-tables issue. 16:38:05 glazou: So what's suggested to rewrite? 16:38:16 Bert: Make it clear what the ancestor box is in all contexts. 16:39:09 TabAtkins: Boris says 3 instances, and I'd *like* to depend on the definition of "ancestor box" in my table issue too. 16:39:18 Bert: If it's only in chapter 10, i can do it. 16:39:20 http://wiki.csswg.org/spec/css2.1#issue-144 16:40:20 yep 16:40:34 TabAtkins: I don't think we need to worry about 144 - it's pointed out that the reporter's results were from looking at it in quirks mode; the spec defines it precisely and all browsers agree in standards mode. 16:40:41 http://wiki.csswg.org/spec/css2.1#issue-145 16:40:45 glazou: So no action on this. Any objections? 16:40:57 RESOLVED: No action on 144 - not a problem. 16:41:37 fantasai: The i18nWG has been going back and forth on issue 145 for a while. 16:42:15 fantasai: We probably need to defer this for them. 16:42:36 http://wiki.csswg.org/spec/css2.1#issue-147 16:42:41 TabAtkins: i18n is having a meeting for bidi in html second week of june that elika and i are attending. We can make sure it's discussed then. 16:43:49 fantasai: It makes sense to recommend scaling for images, but not necessarily for java applets, etc. 16:44:09 fantasai: Sometimes you just want to rescale the box and just tell the replaced element to redraw itself in the new space. 16:44:15 fantasai: Frex, java applet or iframe. 16:44:48 fantasai: So I don't think it makes sense to specify how a replaced element draws in normative terms here. 16:45:06 TabAtkins: Agreed. 16:45:18 RESOLVED: No change for issue 147 16:45:26 http://wiki.csswg.org/spec/css2.1#issue-153 16:46:53 TabAtkins: I think the test case just needs to be updated, no spec change, right? 16:46:59 glazou: elika says the spec is vague. 16:47:20 TabAtkins: Ah, yes, I see that now. 16:48:13 glazou: Any objections to elika's proposal? 16:48:21 arronei: That means the test case needs to be updated too. 16:48:30 TabAtkins: Elika already provided an updated test case. 16:48:44 RESOLVED: Accept Elika's proposal to resolve issue 153. 16:49:08 Action Elika: Write text for 153. 16:49:08 Created ACTION-235 - Write text for 153. [on Elika Etemad - due 2010-06-02]. 16:49:36 http://lists.w3.org/Archives/Public/www-style/2009Dec/0322.html 16:49:46 fantasai: Wrt the previous issue, 147, there's an email not tracked in the issue list pointing out a sentence that doesn't make any sense at all. 16:50:25 fantasai: I think it should be removed, and Tantek agrees. 16:50:48 Bert: I don't see what's wrong with it. 16:50:59 fantasai: If you specify a height, the width of the replaced element's box may not be intrinsic. 16:51:05 Bert: Oh, in that sense. 16:51:34 fantasai: It's weird, and it doesn't add anything since everything is otherwise specified. So I think we should just remove it. 16:51:57 RESOLVED: Remove the offending sentence in visudet. 16:52:12 http://wiki.csswg.org/spec/css2.1#issue-157 16:53:28 TabAtkins: I don't think it's circular. I think it can look like it to a surface reading, but it's just a statement of constraints. 16:53:39 glazou: dbaron and bert have long messages explaining why it's not circular. 16:53:46 fantasai: Bert has a nice examle that I think would clarify things. 16:53:53 glazou: Can you add the example to the spec? 16:54:16 RESOLVED: Add Bert's example about clearance, otherwise no change for issue 157. 16:54:31 http://wiki.csswg.org/spec/css2.1#issue-158 16:54:33 ACTION Bert: Add example about clearance for issue 157. 16:54:33 Created ACTION-236 - Add example about clearance for issue 157. [on Bert Bos - due 2010-06-02]. 16:57:10 TabAtkins: This isn't even a change, just a clarification. 16:57:21 ACTION Tab: Suggest text to resolve issue 158. 16:57:21 Created ACTION-237 - Suggest text to resolve issue 158. [on Tab Atkins Jr. - due 2010-06-02]. 16:57:22 http://wiki.csswg.org/spec/css2.1#issue-159 16:58:37 TabAtkins: dbaron already has some rough text to resolve the issue. 16:58:49 fantasai: I can take this; I'll probably be doing other margin-related things anyway. 16:58:53 http://wiki.csswg.org/spec/css2.1#issue-114 16:59:01 ACTION Elika: Propose text to resolve 114. 16:59:01 Created ACTION-238 - Propose text to resolve 114. [on Elika Etemad - due 2010-06-02]. 16:59:16 glazou: Anyone know what SVG is doing about 114? 16:59:22 arronei: Chris sent me a message about it yesterday. 16:59:29 glazou: So they're working on it, excellent. 17:00:35 -arronei 17:00:37 -smfr 17:00:39 -fantasai 17:00:39 smfr has left #css 17:00:44 -howcome 17:00:50 -CesarAcebal 17:00:55 -bradk 17:00:57 -Bert 17:01:00 Zakim, who is on the phone 17:01:00 I don't understand 'who is on the phone', glazou 17:01:15 Zakim, who's here? 17:01:15 On the phone I see plinss, glazou, TabAtkins, sylvaing 17:01:17 On IRC I see howcome, alexmog, murakami, oyvind, sylvaing, RRSAgent, Zakim, glazou, Curt`, DanC, CesarAcebal, plinss_, arronei, anne, krijnh, Hixie, karl, lhnz, jdaggett_afk, 17:01:19 ... lgombos, TabAtkins, jgraham, fantasai, plinss, Bert, trackbot 17:01:45 zakim, drop sylvaing 17:01:45 sylvaing is being disconnected 17:01:46 -sylvaing 17:05:38 -TabAtkins 17:05:44 -glazou 17:05:45 -plinss 17:05:46 Style_CSS FP()12:00PM has ended 17:05:48 Attendees were plinss, glazou, +49.238.aaaa, CesarAcebal, Bert, TabAtkins, arronei, sylvaing, smfr, fantasai, bradk, +47.23.69.aabb, howcome 17:07:58 murakami has left #css 17:14:40 arronei has joined #CSS 19:18:26 Zakim has left #CSS 19:58:12 jdaggett has joined #css 21:04:25 jdaggett has joined #css 21:18:06 Lachy has joined #css 21:18:59 shepazu has joined #css 23:08:19 Hixie has joined #css