15:23:03 RRSAgent has joined #css 15:23:03 logging to http://www.w3.org/2011/05/25-css-irc 15:23:12 Zakim, this will be Style 15:23:12 ok, glazou; I see Style_CSS FP()12:00PM scheduled to start in 37 minutes 15:23:17 RRSAgent: make logs public 15:42:14 dbaron has joined #css 15:50:14 stearns has joined #css 15:58:02 Style_CSS FP()12:00PM has now started 15:58:07 +??P2 15:58:12 Zakim, ??P2 is me 15:58:12 +glazou; got it 15:59:42 + +1.206.550.aaaa 15:59:59 Zakim, aaaa is me 15:59:59 +stearns; got it 16:00:36 +[Microsoft] 16:00:49 zakim, microsoft has me 16:00:55 +arronei; got it 16:01:14 +[Microsoft.a] 16:01:30 +sylvaing 16:01:30 johnjan has joined #css 16:02:00 +fantasai 16:02:18 Cathy has joined #css 16:02:45 + +1.650.253.aabb 16:02:46 acebal has joined #css 16:02:55 zakim, aabb is me 16:02:55 +TabAtkins; got it 16:03:12 +Bert 16:03:18 +Cathy_Chan 16:04:31 +??P33 16:04:39 zakim, ??p33 is me 16:04:39 +kojiishi; got it 16:04:54 ScribeNick: TabAtkins 16:04:56 Zakim, microsoft has johnjan 16:04:56 +johnjan; got it 16:05:16 glazou: Extras for today? Bert sent one. 16:05:43 + +34.14.4.aacc 16:05:44 glazou: Let's start with the CSS 2.1 pub request. 16:06:01 zakim, aacc is me 16:06:01 +acebal; got it 16:06:16 Bert: There was an internal meeting about the 2.1 review, all comments were positive. 16:06:34 oyvind has joined #css 16:06:38 +dbaron 16:07:51 + +1.858.354.aadd 16:09:25 glazou: Another thing you mentioned was the acks section. 16:09:40 glazou: I suggested listing the current members of the WG. 16:09:56 glazou: Because some former members of the WG are not listed, or people from www-style. 16:10:14 Bert: If people have names to add, please give them to me quickly. 16:10:24 Bert: Especially anyone who's sent lots of issues in LC. 16:11:18 fantasai: I think it's fine to list people who contribute to the testsuite. 16:11:31 fantasai: Maybe in a separate section, specifically titled? 16:11:53 +howcome 16:12:01 fantasai: I don't think listing *all* WG members is a very honest thing to do, because there's a significant number of members who have never sent an email or attended a telcon. 16:12:19 glazou: I don't like the "don't put anything" option, because it misrepresents the work the w3c members have done on this document. 16:12:30 glazou: Bert, I'll mail you a compromise after the call. 16:12:43 sylvaing: Did you get the testimonial from MS? 16:12:52 Bert: Dunno, where did it come from? 16:13:10 sylvaing: From Michael Champion. 16:14:02 plinss_: I'd like to add the links to the annotation system to the spec. 16:14:55 arronei: I presume Bert will produce a diff from the last draft to the PR? 16:15:10 Bert: I hadn't thought about how to make it public yet, any ideas? 16:15:28 arronei: Hadn't thought. I don't particularly need it public yet, so we can get it quickly and then deal with public later. 16:15:51 http://wiki.csswg.org/planning/japan-2011 16:16:02 glazou: Please update the page with your arrival, etc. 16:16:32 glazou: f2f agenda items, we have 9 including stuff coming from the forum. 16:17:26 TabAtkins: I'm definitely going to want to talk about Variables/Mixins/etc 16:18:06 sylvaing: I think Feature Queries in the backlog is an interesting topic. 16:18:16 howcome: We'd like to talk about the CSS Viewport spec. 16:18:40 glazou: I know Anne is on vacation, but do you think he'll have time to contribute to CSSOM when he's back? 16:18:44 howcome: That's my assumption. 16:18:59 glazou: Good, I've been playing with it and it's a huge pain. 16:19:30 sylvaing: It definitely needs some talking about. It needs the 2.1 treatment, but it needs to move forward to new areas as well. 16:19:48 howcome: I think Anne's goal has been to describe something more than what exists today. 16:19:58 plinss has joined #css 16:20:01 howcome: From our perspective, the CSSOM his high priority too. 16:20:35 sylvaing: I think the discussion should be about how to take this gigantic editors draft and get it to move forward. 16:21:12 glazou: It's going to take time, but it's worth doing it. 16:21:36 glazou: I'm going to start mailing the list about issues I've found with it. 16:21:58 howcome: The most important thing from our perspective is to offer alternative to the string-based api. 16:22:05 TabAtkins: Big priority for us too. 16:22:13 glazou: Yes, definitely. Tons of serialization. 16:22:42 glazou: Anything else about the f2f? 16:22:49 glazou: Now, publication requests. 16:22:57 glazou: First is about Writing Modes. Elika requested an LCWD. 16:23:10 fantasai: jdaggett suggested to wait and just publish a WD. 16:23:29 fantasai: I'm fine with that, so we can talk over the issues at the f2f and publish again afterwards. 16:23:35 glazou: I'm fine with that. 16:23:42 RESOLVED: Publish Writing Modes as WD. 16:23:47 glazou: Anyone from Adobe on the call? 16:24:01 We have a request for Regions & Exclusions. 16:24:19 glazou: Lots of discussion about this on the lsit, and Vincent said he was integrating the feedback. Is that done? 16:24:35 stearns: Not sure if he's finished that yet, but I know he's working on it. 16:25:07 fantasai: I think there was a lot of discussion about merging or splitting Exclusions into/from Floats, so if Regions is ready it makes sense to publish, but we should wait for Exclusions until after the f2f. 16:25:16 arronei: I agree. 16:25:27 alexmog: Me too. 16:25:32 alexmog has joined #css 16:26:03 RESOLVED: Once the WG gets an email saying that Regions edits are done, publish as WD. 16:27:33 glazou: Next, publishing Images. 16:28:09 fantasai: should have a changes list 16:28:15 Tab: I'd like to resolve on gradient angles. 16:28:22 Daniel: probably better at F2F 16:28:35 http://www.css3.info/angles-in-gradients/ 16:28:41 fantasai: Got some Web author feedback on this issue (url) 16:28:56 Tab: overwhelming majority go in one direction, which is how I've now changed the spec 16:29:02 95 comments 16:29:24 Tab: now it's 0deg is north, 90deg is east, clockwise... 16:29:52 glazou: Next is CSS3 Namespaces. 16:30:08 glazou: We were supposed to get some comments from i18n, and still have nothing so far. 16:30:15 fantasai: I see the draft response on their list. 16:30:49 fantasai: They give some background information, and recommend that Namespaces say that selectors should be compared as canonically equivalent. 16:31:02 fantasai: I replied saying that was out-of-scope for this draft, because we don't deal with selector matching in Namespaces. 16:31:10 glazou: Can you mail the list with references to these two emails? 16:31:38 fantasai: The in-scope issue that they could make would be that namespace prefixes should be canonicalized. 16:31:50 glazou: Do we fall into normalization hell? 16:32:23 fantasai: I think that if we wanted to address their concern if would be relatively straightforward to require that all CSS identifiers are parsed into NFC or whatever. Normalize on parsing, and just store it that way from then on. 16:32:50 glazou: I think I remember a comment from david that normalizing at parse time is going to be very expensive. 16:33:20 dbaron: I remember a discussion where I said I'd much rather normalize strings than normalize later - I'd rather do it at the same time we do encoding conversion and such. 16:33:34 glazou: So if we store all identifiers in a given normalization, is that okay? 16:34:16 dbaron: I was suggesting encoding-time normalization - authors could still manually get unnormalized things by using escape chars. 16:34:20 glazou: Could you suggest some text? 16:34:37 dbaron: I think this is higher-level than namespaces. 16:34:50 dbaron: And I think we need good agreement between browsers that they're willing to do. 16:35:07 glazou: Ok. The comment that it's something that must be addressed at a higher level is a good comment for us. 16:35:27 glazou: Elika, please mail references to the two emails, and I'll write prose saying what dbaron just said. That way we can move the document along the rec track. 16:35:57 fantasai: Okay. Also, I think dbaron's suggestion makes a lot of sense. 16:36:08 http://lists.w3.org/Archives/Public/public-i18n-core/2011AprJun/0077.html 16:36:45 fantasai: So everyone should ping their parser guys and see what they think. 16:36:59 glazou: Whatever the answer, we can say that the issue shouldn't be addressed for the Namespaces spec itself. 16:37:52 fantasai: We can potentially say that namespace prefixes specifically are canonicalized. But we'd have to reject that suggestion to say that the greater issue is out of scope. 16:38:28 glazou: At some point I'd like to discuss the OM for namespaces. Right now we have nothing, and it makes it impossible to serialize a stylesheet. 16:38:54 glazou: We have a few technical items on the wiki to discuss still. 16:39:14 fantasai: Did we go over the website? 16:41:01 [uncaught talk about alternate stylesheets?] 16:41:12 for comparison, here's the design submitted by Divya 16:41:16 http://csswg.inkedblade.net/staging/redesign/index-divya.html 16:41:34 Bert said to go to http://www.w3.org/Style/CSS/ 16:41:40 glazou: So, should we switch? I say yes. 16:41:41 and switch the alternate style sheet to "Main" 16:41:43 TabAtkins: Yes. 16:41:44 arronei: Yes. 16:41:49 yes 16:41:59 Bert: Anyone, please check for errors or anything I can improve. 16:42:28 Bert: I plan to turn it on before I leave for Japan, so sometime Monday. 16:42:42 RESOLVED: Change the website over to the new design from Divya. 16:42:55 glazou: A companion item - the csswg blog. 16:43:07 glazou: "What will it take to switch to wordpress?" 16:43:15 Bert: On the tech side, it's easy, just put in a sysreq. 16:43:38 fantasai: Can we please do that? It would be amazingly easy. 16:43:55 Bert: The only thing I'm unsure of is how to do templates. 16:43:57 s/easy/wonderful/ 16:44:18 fantasai: If the only thing we're blocked on is getting a wp template, we can do that. 16:44:55 glazou: We'll just need the template before the switch. 16:45:08 fantasai: I'll be the point person, but I can't do the template myself. 16:45:15 glazou: Ok, let's do the coordination offline.