15:07:14 RRSAgent has joined #CSS 15:07:14 logging to http://www.w3.org/2010/06/23-CSS-irc 15:10:26 Curt` has joined #css 15:51:32 dethbakin has joined #css 15:53:50 zakim, this will be style 15:53:51 ok, plinss; I see Style_CSS FP()12:00PM scheduled to start in 7 minutes 15:54:02 rrsagent, make logs public 15:54:35 oyvind has joined #css 15:55:18 sylvaing has joined #css 15:56:43 hi plinss 15:56:57 hello 15:58:25 bradk has joined #css 15:58:46 Style_CSS FP()12:00PM has now started 15:58:53 + +1.858.216.aaaa 15:59:05 zakim, aaaa has plinss 15:59:05 +plinss; got it 15:59:10 smfr has joined #css 15:59:12 Zakim, aaa has glazou 15:59:12 sorry, glazou, I do not recognize a party named 'aaa' 15:59:16 zakim, aaaa has galzou 15:59:16 +galzou; got it 15:59:21 lol 15:59:34 Zakim, galzou is me 15:59:34 sorry, glazou, I do not recognize a party named 'galzou' 15:59:43 zakim, who is on the phone? 15:59:43 On the phone I see +1.858.216.aaaa 15:59:44 +1.858.216.aaaa has galzou 15:59:51 + +1.650.275.aabb 15:59:56 + +1.650.253.aacc 16:00:02 Zakim, aacc is me. 16:00:02 +tabatkins; got it 16:00:08 +[Apple] 16:00:17 Zakim, Apple has dethbakin 16:00:17 +dethbakin; got it 16:00:27 Zakim, aabb is me 16:00:27 +bradk; got it 16:00:28 zakim, aaaa is [plinss] 16:00:29 +[plinss]; got it 16:00:38 zakim, [plinss] has glazou 16:00:38 +glazou; got it 16:00:44 zakim, who is on the phone? 16:00:44 On the phone I see [plinss], bradk, tabatkins, [Apple] 16:00:46 [plinss] has glazou 16:00:47 [Apple] has dethbakin 16:01:31 +fantasai 16:01:31 + +1.206.324.aadd 16:01:46 Zakim, aadd is sylvaing 16:01:47 +sylvaing; got it 16:01:50 Zakim, aabb is bradk 16:01:50 sorry, glazou, I do not recognize a party named 'aabb' 16:02:10 Zakim, your sick bridges turn you mad 16:02:10 I don't understand 'your sick bridges turn you mad', glazou 16:02:48 + +1.408.636.aaee 16:02:56 Za-kim has me, unless Tab and I got ourselves mixed up (same area code appearing at about same time) 16:02:59 Zakim, aaee is me 16:02:59 +smfr; got it 16:03:41 sylvaing: almost turned JSCSSP into a CSS 3 validator... 16:04:38 zakim, mute tabatkins 16:04:38 tabatkins should now be muted 16:04:53 zakim, unmute tabatkins 16:04:53 tabatkins should no longer be muted 16:05:07 glazou: we need eCSSxtender to use your parser. Darn thing uses regex 16:05:13 :) 16:05:31 sylvaing: yeah, I am implementing my own when I save a stylesheet :-) 16:06:01 but no solution for inline styles still rendering engines use a serialized version of inline styles there 16:06:25 ScribeNick: TabAtkins 16:06:41 +SteveZ 16:07:12 glazou: Elika, test suite status? 16:07:30 szilles has joined #css 16:07:41 fantasai: Status is we published alpha 3 last week. There's a bunch of moz tests that still need to be imported. Aaron says he's fixed the ones that were wrong, but there still might be one or two problems. 16:08:03 fantasai: I'll try and publish beta 1 next week, and we'll ask people to review them and make sure everyone is happy getting implementation reports based on them. 16:08:12 fantasai: We plan to get implementation reports in before the ftf. 16:08:23 fantasai: We plan to publish on a 3week cycle. 16:08:31 glazou: You tweeted something about reftests. Is that related? 16:08:37 fantasai: No, that was me working with moz stuff. 16:08:50 glazou: We have roughly 20 issues that are still undiscussed or lack a proposal. 16:09:16 glazou: I think the first one up is issue 53. 16:09:33 http://lists.w3.org/Archives/Public/www-style/2008Jun/0227.html 16:09:33 http://wiki.csswg.org/spec/css2.1#issue-53 16:09:55 glazou: Elika, this is something you posted. 16:11:27 tabatkins: Elika's proposal sounds great, that glyphs and whitespace in pre aren't altered for justification purposes. 16:11:39 szilles: So that says that pre is more powerful than justification? 16:11:41 glazou: Yes. 16:12:09 fantasai: I don't quite understand why you can't justify pre-wrap, since it wraps, but I'd be fine with something that just said you can't stretch spaces. 16:12:28 szilles: I thought that if the spacing are there even with the wrap, you might have columns that you don't want to go jagged. 16:12:48 you don't want to mess up Bert's ASCII art. Or Hixie's cat. 16:13:01 szilles: It seems odd anyway to have both pre and justify on an element. 16:13:11 tabatkins: You may have an inline with pre embedded in a justified element. 16:13:21 http://lists.w3.org/Archives/Public/www-style/2010Jun/0457.html 16:13:25 ^^^ proposed solution 16:14:54 fantasai: We usually write plaintext in monospace to get things to line up. But if you're using pre-wrap, maybe you're just writing paragraphs, and would be okay with justifying. 16:15:10 fantasai: pre-line is definitely wrong in the spec and should be fixed. But pre-wrap, I'm not sure of. 16:15:30 fantasai: One thing we could say is that you're not required to justify in preformatted elements. 16:15:41 fantasai: And then maybe in css3 text we can clarify it more precisely. 16:15:57 glazou: I like that. 16:16:16 bradk: Are the other text-align values okay? 16:16:32 tabatkins: According to the proposal on the table, no, you can't right-align pre text. 16:16:44 tabatkins: Nm, I'm misreading. 16:17:21 glazou: Any particular objections to the proposal on the table? 16:17:29 tabatkins: Elika has a possible objection for the pre-wrap text. 16:17:47 glazou: I'll ping Thunderbird people for an answer on what's acceptable to them, since it may affect email. 16:18:16 ACTION Daniel: Ping Thunderbird for their input on how the changes to the spec around pre/pre-wrap and justification may affect email. 16:18:17 Created ACTION-240 - Ping Thunderbird for their input on how the changes to the spec around pre/pre-wrap and justification may affect email. [on Daniel Glazman - due 2010-06-30]. 16:19:30 fantasai: We can just say that justification isn't required. 16:19:40 tabatkins: I'd prefer not having it be impl-defined. 16:20:14 sylvaing: If the impls are disagreeing today, isn't it possible that email clients right now are having problems? 16:20:25 tabatkins: Only if they're mixing it with justification, which I doubt anyone is right now. 16:20:32 glazou: Next issue is 101, assigned to dbaron. 16:20:45 http://wiki.csswg.org/spec/css2.1#issue-101 16:20:50 Next one for the wg is 107. 16:20:54 http://wiki.csswg.org/spec/css2.1#issue-107 16:22:33 fantasai: The cases that this affects are where you're inheriting top/bottom/left/right, which almost nobody does. 16:22:46 fantasai: The proposal is to clarify the spec so that it's consistent with impls. 16:22:54 glazou: And all impls do the same thing? 16:23:24 fantasai: Yeah, me and aaron put some testcases. 16:23:57 fantasai: And this is such a minor issue that I doubt it matters what we actually do, so long as it's specified. 16:24:12 RESOLVED: Accept fantasai's proposal for resolving issue 107. 16:24:17 glazou: Next is issue 110, on Tab. 16:24:27 tabatkins: Haven't been able to write up a new proposal, sorry. 16:24:35 glazou: Next is issue 120. 16:25:02 fantasai: That'll take a while, since I have to go through the whole spec. 16:25:41 fantasai: There are like 4 issues on me that I need to deal with still. 16:25:45 glazou: Issue 138, on tab. 16:25:59 tabatkins: I wrote a proposal some time ago, I just didn't put it on the wiki. I've done that now. 16:26:18 glazou: Everyone, read that and review for decision soon. 16:26:56 glazou: Next is issue 145. 16:27:15 tabatkins: I recall us discussing that during the BIDI meeting. 16:27:47 fantasai: Proposal on the table addressing the issue I identified during the bidi meeting. 16:28:08 RESOLVED: Accept fantasai's proposal for resolving issue 145. 16:28:28 glazou: Next on the agenda is issue 149. 16:30:31 szilles: I don't see any possible way to have this resolve any other way. 16:30:42 glazou: At some point we have to decide, and I think the WG decided. 16:31:20 sylvaing: I think the only problem here is that Bert is the gatekeeper of the spec. 16:32:06 fantasai: The issue we haven't discussed here is how this affects Media Queries 16:32:43 fantasai: Frex, on an iphone with a width 2in media query, when does it say yes/no? 16:34:38 sylvaing: For example, at first a webpage on the iphone is zoomed out and full-size, but when you pinch and zoom in, you dont' want the media query to suddenly change, since the webpage is still theoretically the same size. 16:34:45 glazou: Can we just resolve this on media queries? 16:35:20 sylvaing: If we accept the proposal now, we should go ahead and file an issue on media queries, since it's in CR right now. 16:35:37 glazou: So, objections on the proposal? 16:36:04 RESOLVED: Accept fantasai's proposal to resolve issue 149. 16:36:34 RESOLVED: Issue on MQ about possible problems with Media Queries, physical dimenions, and screen sizes. 16:36:46 glazou: Next issue, 151. 16:37:06 fantasai: SVG wants their presentational attributes treated as presentational hints, not as ua stylesheet rules. 16:37:15 fantasai: But right now CSS defines otherwise. 16:37:47 fantasai: So this proposal alters the spec to allow XML languages to have their presentational attributes either be on the preshint level or the ua stylesheet level. 16:38:29 RESOLVED: Accept fantasai's proposal to resolve issue 151. 16:38:34 glazou: Next is issue 153. 16:40:17 fantasai: If you're aligning a replaced alignment to the baseline, it's easy and defined. But for any other alignment, it's unclear which box of the replaced element should be used. 16:40:39 correction: inline non-replaced elements. 16:41:16 dbaron has joined #css 16:41:41 fantasai: I could try and spend more time on getting a proper definition, but I don't know if we could impls in time for CR. 16:41:50 +David_Baron 16:41:53 RESOLVED: Accept fantasai's proposal for resolving issue 153. 16:42:19 dbaron: I was just looking at IRC, and I don't think it needs to be undefined. 16:42:36 dbaron: I think it might have been clearer in CSS1, but I think it was well-defined somewhere. 16:42:45 RESOLVED: ignore previous resolution 16:43:02 ACTION David: Produce a proposal for issue 153. 16:43:02 Sorry, amibiguous username (more than one match) - David 16:43:02 Try using a different identifier, such as family name or username (eg. hyatt, dbaron, dsinger2) 16:43:10 ACTION dbaron: Produce a proposal for issue 153. 16:43:11 Created ACTION-241 - Produce a proposal for issue 153. [on David Baron - due 2010-06-30]. 16:44:12 current issue is 158 16:44:34 http://lists.w3.org/Archives/Public/www-style/2010Jun/0124.html 16:44:55 -[Apple] 16:45:03 I think ^^^ is okay, but I'm still unsure of the exact desired rendering of a particular edge case, so I'm not sure if fantasai's suggestion fits or not. 16:45:05 I can dig up the emails from when we originally came up with that issue 16:45:47 http://dbaron.org/css/test/2007/0329-blog-examples/1 16:45:52 http://lists.w3.org/Archives/Member/w3c-css-wg/2007JanMar/0538.html 16:47:06 glazou: I suggest you two take the discussion offline and clarify this between yourselves. 16:47:14 glazou: Next issue is 159, for elika. 16:48:01 fantasai: I haven't gotten to that yet. 16:48:28 http://wiki.csswg.org/spec/css2.1#issue-160 16:48:51 glazou: Issue 160. This should be easier to resolve. 16:49:17 glazou: The proposal seems to make perfect sense. 16:49:35 RESOLVED: Accept fantasai's proposal for resolving issue 160. 16:49:59 Not done yet 16:50:01 glazou: Issue 166, on Elika. 16:50:14 glazou: Clarify different uses of "property value" and "component value", and make a diff. 16:51:08 fantasai: Haven't been able to get to that yet. 16:51:20 glazou: Issue 167, backslash escapes. 16:52:45 glazou: So, where's the end of a stylesheet, if you "end" one with a backslash? 16:53:05 tabatkins: There isn't interop, so whatever we decide should be okay. 16:53:36 tabatkins: I think it's just a matter of looking over Zack's proposed changes and ensuring they really do have only the minimal impact that he believes. 16:53:54 ACTION Daniel: Look over Zack's proposal for issue 167, ensure that it doesn't have any unwanted effects. 16:53:54 Created ACTION-242 - Look over Zack's proposal for issue 167, ensure that it doesn't have any unwanted effects. [on Daniel Glazman - due 2010-06-30]. 16:54:01 glazou: Next issue, 170. 16:54:44 glazou: dbaron has listed 5 possibilities to resolve it. 16:55:58 dbaron: 6, counting the "leave it explicitly undefined" case. 16:56:04 bradk: Is there any interop on this? 16:58:20 ACTION Tab: Write some tests for issue 170, to see which option seems closest to impls. 16:58:20 Created ACTION-243 - Write some tests for issue 170, to see which option seems closest to impls. [on Tab Atkins Jr. - due 2010-06-30]. 16:58:27 glazou: Next is issue 172. 16:59:04 arronei has joined #CSS 16:59:19 -bradk 16:59:41 DOH. I got dropped. 16:59:42 I don't have a problem with it. Table captions are rare in the first place, and table captions that would overflow are even more so. 17:00:17 ACTION Elika: Propose wording for issue 172. 17:00:17 Created ACTION-244 - Propose wording for issue 172. [on Elika Etemad - due 2010-06-30]. 17:00:18 I'm fine with the proposal 17:00:32 -smfr 17:00:43 -David_Baron 17:00:44 -sylvaing 17:00:46 -SteveZ 17:00:50 smfr has left #css 17:00:52 -[plinss] 17:01:19 that was a very productive conf call I must say 17:01:29 dethbakin has left #css 17:01:47 bye 17:02:29 bye 17:06:57 -tabatkins 17:07:02 -fantasai 17:07:03 Style_CSS FP()12:00PM has ended 17:07:04 Attendees were plinss, galzou, +1.650.275.aabb, +1.650.253.aacc, tabatkins, dethbakin, bradk, [plinss], glazou, fantasai, +1.206.324.aadd, sylvaing, +1.408.636.aaee, smfr, SteveZ, 17:07:07 ... David_Baron 17:44:21 sylvaing has joined #css 18:21:00 Zakim has left #CSS 18:31:50 tabatkins: can you update the 2.1 issues list whenever you send in an issue proposal? 18:35:41 fantasai: Yeah, I need to remember to do so. 18:35:47 I'll update the issue list for 158 now. 18:40:48 dbaron has joined #css 18:52:07 sylvaing has joined #css 19:42:21 plinss_ has joined #css 20:16:27 sylvaing has joined #css 20:16:35 sylvaing has left #css 21:23:25 nimbupani has joined #css 22:33:52 shepazu has joined #css 23:09:56 dbaron has joined #css