16:29:49 RRSAgent has joined #css 16:29:49 logging to http://www.w3.org/2012/02/15-css-irc 16:29:54 RRSAgent, make logs public 16:57:18 Style_CSS FP()12:00PM has now started 16:57:25 +??P41 16:57:31 Zakim, ??P41 is me 16:57:31 +glazou; got it 16:57:51 Zakim, code? 16:57:55 the conference code is 78953 (tel:+1.617.761.6200 sip:zakim@voip.w3.org), shepazu 16:58:18 +Doug_Schepers 16:59:21 + +1.206.550.aaaa 17:00:03 danielweck has joined #css 17:00:11 zakim, aaaa is me 17:00:12 +Bert 17:00:17 antonp has joined #css 17:00:41 arronei has joined #css 17:00:46 +??P53 17:00:49 Zakim, I am ??P53 17:00:54 +stearns; got it 17:00:56 +[Apple] 17:00:56 smfr has joined #css 17:01:08 Zakim, Apple has me 17:01:29 +glenn 17:01:35 Zakim, ??53 is florianr 17:01:44 krit has joined #css 17:02:03 +florianr; got it 17:02:08 +[Microsoft] 17:02:16 Zakim, who is here? 17:02:23 TabAtkins_ has joined #css 17:02:28 +hober; got it 17:02:28 Zakim, who's here? 17:02:32 zakim, bert also has fantasai 17:02:35 -Doug_Schepers 17:02:38 +[IPcaller] 17:02:39 +[Microsoft.a] 17:02:49 Zakim, WAKE UP 17:02:56 Zakim, where are you? 17:03:08 +??P18 17:03:08 I'll be in momentarily. 17:03:10 sorry, glazou, I do not recognize a party named '??53' 17:03:20 +plinss 17:03:21 Zakim, ??P18 is me 17:03:21 ChrisL has joined #css 17:03:26 Zakim, Apple has me 17:03:42 +Present krit 17:03:45 dstorey has joined #css 17:03:58 On the phone I see glazou, stearns, Bert, florianr, [Apple], glenn, [Microsoft], [IPcaller], [Microsoft.a], ??P18, plinss 17:04:01 [Apple] has hober 17:04:11 On the phone I see glazou, stearns, Bert, florianr, [Apple], glenn, [Microsoft], [IPcaller], [Microsoft.a], ??P18, plinss 17:04:16 [Apple] has hober 17:04:20 +fantasai; got it 17:04:32 Zakim, [IPcaller] is me 17:04:32 +[Apple.a] 17:04:43 +??P75 17:04:46 Zakim, [Apple.a] is me 17:04:52 I don't understand 'WAKE UP', glazou 17:04:53 Zakim, ??P18 is me 17:04:56 (trying again) 17:05:00 I don't understand your question, danielweck. 17:05:06 + +93550aabb 17:05:22 Zakim, aabb is me 17:05:24 +danielweck; got it 17:05:38 +smfr; got it 17:05:47 Scribe: fantasai 17:05:57 On IRC I see dstorey, ChrisL, TabAtkins_, krit, smfr, arronei, antonp, danielweck, RRSAgent, Zakim, glazou, kojiishi, glenn, nimbu, SimonSapin, florianr, tantek_, drublic, tantek, 17:06:03 ... karl, arronei_, leaverou, jdaggett, Bert, Hixie, shepazu, stearns, ed, alexmog, shans_away, vhardy, sylvaing_away, plinss, krijnh, macpherson, trackbot, hober, gsnedders, 17:06:04 glazou: Any extra items for today? 17:06:06 ... paul___irish, CSSWG_LogBot, fantasai 17:06:06 Bleh, took enough tries. 17:06:11 ScribeNick: TabAtkins_ 17:06:20 Florian: Not sure howcome is here today; if not, shouldn't talk about GCPM 17:06:30 +krit; got it 17:06:34 glazou: I noted that you posted clarifications about the selectors4 requests. 17:06:38 + +1.415.871.aacc 17:06:41 glazou: Let's move to the first item on our agenda today. 17:06:45 glazou: It's about -webkit- prefix. 17:06:46 +smfr; got it 17:06:53 glazou: I had a lot of chats between the first day and yesterday. 17:06:55 I already had ??P18 as danielweck, danielweck 17:06:59 Zakim, aacc is tantek 17:06:59 howcome has joined #css 17:07:01 glazou: That ended with the proposal I made to Brendan. 17:07:09 glazou: A compromise about what we could do in this WG. 17:07:12 glazou: Brendan Eich. 17:07:23 glazou: This was discussed between Brendana nd Jeff Jaffe on Monday. 17:07:26 +antonp; got it 17:07:34 glazou: I don't know the details, but apparently the compromise goes in the right direction. 17:07:40 glazou: So we need to discuss and find a plan here. 17:07:43 + +1.650.253.aadd 17:07:56 glazou: If it's so urgent that the three browser vendors raised in Monday, we need to move forward quickly. 17:08:00 linky please 17:08:01 + +1.206.552.aaee 17:08:05 +tantek; got it 17:08:19 SteveZ has joined #css 17:08:31 http://www.w3.org/mid/4F391911.307@disruptive-innovations.com 17:08:37 to be clear - I was at that meeting with Jeff Jaffe and Brendan on Monday 17:08:50 Zakim has kicked me out 17:08:54 unable to join-in 17:09:05 dbaron has joined #css 17:09:08 glazou: That's not a decision, it's a proposal to discuss. 17:09:15 glazou: It merely seemed reasonable at the time I wrote it. 17:09:21 I'm getting a busy signal dialing Zakim 17:09:24 glazou: I'd like to discuss this, and if you have counterproposals, discuss those. 17:09:32 SteveZ has joined #css 17:09:35 sylvaing: What's the connection between this and what Brendan and Jeff discussed? 17:09:37 glazou: No idea. 17:09:45 Zakim says: "enable to take your call, try again later" 17:09:45 JohnJansen has joined #css 17:09:46 tantek: I was at the meeting. We discussed daniel's proposal. 17:09:56 tantek: I don't think anything new came out of that; it was just Jeff gaining a broder understanding. 17:10:12 tantek: The key point is the one I made in email - we don't have a specific list yet, and I don't think anyone has yet. 17:10:20 SteveZ has joined #css 17:10:30 florianr: I don't think anyone has a final list, but we should be able to give a top-5 list or something. 17:10:53 tantek: I can put it in a more coarse-grained fashion. We're still analyzing our data, and we don't have specific properties to propose yet. 17:10:57 Rossen has joined #css 17:11:13 tantek: It would be very helpful for us and the group if certain specs were made to advance more quickly. 17:11:18 tantek: Because the syntax is stable. 17:11:24 florianr: I have a questiona bout your studies. 17:11:41 florianr: It seems that with even a little bit of study, it seems easy to come up with a simple list of stuff applicable everywhere. 17:11:47 florianr: So what info are you looking for? 17:12:00 tantek: We also find that when -webkit-border-radius is used, there's also the other prefixes or unprefixed. 17:12:12 tantek: So the result is, how much difference would it amek to implement -webkit-border-radius? 17:12:20 tantek: if the answer is "not that much difference", it's not worth doing. 17:12:29 tantek: So it's the question of what it's used with. 17:12:35 tantek: If we can avoid supproting -webkit-, great. 17:13:06 tantek: When we do find a property that seems to be -webkit- prefixed only, the question is: 17:13:12 tantek: Is it affecting the user, and hwo much? 17:13:24 tantek: And that's a hard question to answer without manually looking at the site. 17:13:33 tantek: If you can't tell the difference, what's the point of implementing it? 17:13:42 tantek: So we're trying to be conservative here. 17:14:05 tantek: The coarse data alone, though, provides us enough clues to reccommend to the WG which specs to advance faster. 17:14:28 florianr: I've done some studies here. I don't think there as details as yours, but I've looked for whether -webkit- is used with or without something else that opera supports. 17:14:34 glazou: Can you share this data? 17:14:39 florianr: I've sent it to the private list. 17:14:47 http://www.w3.org/mid/op.v9n5gsan4p7avi@localhost.localdomain 17:15:27 glazou: Are you making a big difference between border-radius, whichi is specified and implemented everywhere, and between properties that are more experiemental, have little or no spec, and not implemented anywhere else. 17:16:09 glazou: For the former, the decision to impelment -webkit- is only in your hands. There's nothing we can do on the standards side. 17:16:17 glazou: For the latter, we need more specs, we need faster movement. 17:16:32 florianr: There's a third case,w hich is important - things that are on progress, but not prefixed yet. 17:16:39 -danielweck 17:16:44 glazou: For the second case, I think we have a problem. Most of them come from Apple. 17:16:53 glazou: The current specs available online are really light, to say the least. 17:16:59 florianr: Like text-size-adjust? 17:17:03 glazou: Not only that, but yes. 17:17:09 did florianr say "not unprefixed yet" rather than "not prefixed yet"? 17:17:11 glazou: I think the definition is underspecified, to say the least. 17:17:27 florianr: From my data, text-size-adjust comes first among things without a spec, -webkit-appearance is next. 17:17:37 sylvaing: When you crawl, what UA string are you using? 17:17:45 florianr: wget's UA string. 17:17:56 sylvaing: On the mobile web, you get very different content based on the UA string. 17:18:10 sylvaing: If you pretend to be webkit, the results are completely different. 17:18:19 sylvaing: So we're trying to figure out which method to use to report the numbers. 17:18:41 [time check: 2 mins left on this issue; what are we trying to achieve?] 17:18:45 florianr: I've seen people doing mroe sophisticated analysis, and the numbers were higher if they spoofed as webkit, but the ordering was pretty similar to my method. 17:18:59 glazou: So, what are we going to do *now*? 17:19:14 glazou: We need specs for the underspecified properties, and we need analysis for the ones that need to go faster. 17:19:26 tantek: I think there are 3 specs that the WG needs to publish as LC asap. 17:19:37 tantek: And ocnsider dropping prefixes early since the syntax is stable. 17:19:44 tantek: Transforms, Transitions, and Animations. 17:19:48 glazou: 2d or 3d? 17:19:52 tantek: I think 2d. 17:19:58 -smfr 17:19:59 tantek: Based on the wG discussion to split 2d and 3d. 17:20:12 oops 17:20:24 sylvaing: I think we agreed to try and advance them together, because it would be more work to pull them apart. 17:20:31 smfr, you're not going to be able to dial in again, either 17:20:44 just did 17:20:46 +[Apple.a] 17:20:53 florianr: going back to the things without a spec, I thinkw e're counting on webkit people to submit a spec for -webkit-text-size-adjust. 17:21:06 florianr: And appearance was dropped from CSS3 UI with the intent to be in CSS4 UI. 17:21:12 That said, Zakim is actually *ringing* now, which is better than before. 17:21:13 florianr: Analysis suggests it's being used. 17:21:36 I don't think appearance was dropped with intent to be in css4-ui. 17:21:38 tantek: I agree that it would be good to see proposals from Webkit about text-size-adjust, at least a simple draft. 17:21:42 I think it was dropped because some people objected to the principle. 17:22:10 tantek: On appearance, based on my prop there's very little interop. Most seem to be using it for appearance:none. But I don't think there was much actual impact of using it. 17:22:21 tantek: So I thinkt he highest impact is text-size-adjust and the three specs I mentioned. 17:22:31 glazou: So let's focus on those three specs and text-size-adjust. 17:22:38 glazou: It seems that the syntax is not going to change. 17:22:49 glazou: So can we unprefix and move them forward fast? 17:22:59 smfr: At the f2f we decided *not* to split the transforms specs. 17:23:23 I think we should just try to move all of transforms forward quickly. 17:23:24 smfr: And we have some demands for lTransforms syntax changes. 17:23:43 Tab: Let's move transforms forward. We can adjust syntax later. 17:23:52 We should reject the demands for syntax changes 17:24:31 glazou: So do we agree to move the Transforms spec without the syntax change? 17:24:42 smfr: Are yout alking about combiend 2d/3d/svg transforms spec? 17:24:50 glazou: Yes. 17:25:03 smfr: Are we going to wait for feedback from SVg, or define some conformance classes? 17:25:33 tantek: Has anyone shipped support for the new features? 17:25:34 smfr: No. 17:26:22 Dirk: The only difference is the three argument rotate(), so I don't think it makes sense to split from SVG right now. 17:26:26 presumably transforms will go to LCWD before CR, yes? 17:26:33 I think the three argument rotate() should be reverted. 17:26:36 In the context of a sepc jointly edited by SVG and CSS folks, how are you "waiting for feedback" from SVG 17:26:43 glenn, yes, that's required 17:26:46 +[Mozilla] 17:26:47 tantek: I'm not opposed to new things in the future, but I think it should be at minimum split into a separate WD and published later. 17:26:49 Zakim, [Mozilla] is dbaron 17:26:49 +??P7 17:26:50 +dbaron; got it 17:26:56 tantek: Or marked it as at-risk and keep moving, knowing it might not exit CR. 17:27:04 zakim, ??p7 is me 17:27:04 +kojiishi; got it 17:27:12 smfr: The other issue is that we can't drop prefixes on 2d unless we start prefixing the 3d functions. 17:27:17 smfr: Which will be confusing for authors. 17:27:32 tantek: Why is it difficult if we have interop on 2d? 17:27:35 all the options are confusing to authors in some way 17:27:39 florianr: The prefixes are on the property, not the value. 17:27:46 prefixing 3d seems the least confusing option 17:28:10 glazou: I think the 3d functions are already too spread on the web to worry about it. 17:28:16 florianr: so to unprefix 2d only, you'd have to prefix the 3d functions 17:28:24 florianr: which would be confusing for authors 17:28:31 +ChrisL 17:29:15 sylvaing: I would like a testsuite before we claim interop. 17:29:46 TabAtkins_: Do ytou expect any lack of interop to affect the syntax? 17:29:54 [unminuted talking over each other] 17:29:54 +1 to tantek's proposal 17:30:03 sylvaing: It's just about splitting 2d/3d. 17:30:15 is there anything new here that we didn't discuss at the F2F? 17:30:22 tantek proposes moving to lcwd asap and dropping prefixes at lcwd for this spec 17:30:28 tantek: I'm not talking about exitting CR right now, just unprefixing. 17:30:51 q+ fantasai 17:31:20 + +47.21.65.aaff 17:31:22 sylvaing: Are we making an exception to the unprefixing rule? 17:31:24 tantek: Yes. 17:31:54 glazou: Last week we discussed de facto vs de jure standards. These are de facto standards already. 17:32:39 [bankrupcty] 17:33:24 sylvain: We have rules for dropping prefixes and I'm asking why we're making an exception? 17:33:33 TabAtkins_: Back to the discussion. Transform, Transitions, Animations. Drop prefixes? 17:33:42 TabAtkins_: Can we poll on this? Discussion seems to be going nowhere. 17:33:50 Zakim, who is on the phone? 17:33:50 On the phone I see glazou, stearns, Bert, florianr, [Apple], glenn, [Microsoft], krit, [Microsoft.a], plinss, ??P75, antonp, tantek, +1.650.253.aadd, +1.206.552.aaee, [Apple.a], 17:33:54 ... dbaron, kojiishi, ChrisL, howcome 17:33:54 [Apple] has smfr 17:33:54 Bert has Bert, fantasai 17:34:07 Poll options: 17:34:07 Zakim, aaee is me 17:34:07 +nimbu; got it 17:34:11 Zakim, Apple.a has me 17:34:11 +hober; got it 17:34:16 1) Move Transforms/Transitions/Animations to LC and allow unprefixing. 17:34:18 Zakim, Microsoft.a is me 17:34:18 +Rossen; got it 17:34:42 2) No exception, just try to move the specs fast. 17:35:22 If we're making an exception to the process, we should document that in the Snapshot *as an exception* 17:35:29 glazou: 1 17:35:33 chris option 1 17:35:35 glenn: 2 17:35:38 astearns: 1 17:35:47 bert: 2 17:35:54 florianr: 1 17:36:28 dirk: Does option 1 mean no more syntax changes? 17:36:32 TabAtkins_: Yes. 17:36:34 smfr: 2 17:36:46 sylvaing: 2 17:36:55 nimbu: 1 17:37:01 plinss: Torn, but 2. 17:37:04 antonp: 2 17:37:07 tantek: 1 17:37:07 Rossen: 2 17:37:13 TabAtkins_: 1 17:37:14 howcome: 1 17:37:17 -Rossen 17:37:18 dbaron: 1 17:37:21 hober: 2 17:37:22 arronei: 2 17:37:22 krit: 2 17:37:25 jet has joined #CSS 17:37:35 davidStorey: 1 17:37:45 :) 17:37:58 -webkit-3? 17:38:05 +[Microsoft.a] 17:38:15 Zakim, Microsoft.a is me 17:38:15 +Rossen; got it 17:39:06 q+ 17:39:07 fantasai: My preference woudl be to list the transforms functions we're trying to unprefix in the Exceptions clause, and work on the spec knowing that we are syntax-constrained. 17:39:25 s/Exceptions clause/exceptions clause in the snapshot/ 17:39:40 fantasia is voting for a modified 1 which may allow syntax changes f there are issues 17:39:49 ... to avoid multiple last calls 17:39:54 SteveZ has joined #css 17:40:13 I agree with fantasai 17:40:36 Yes, I'm happier with fantasai's modified (1) than with the original (1). 17:40:39 (I think 3 is like 1, except that we explicitly reserve (and warn!) the right to change the syntax again.) 17:40:55 3) move to LCWD, try to freeze syntax, unprefix, but still correct issues if they arise in LCWD 17:41:11 fantasai: I don't agree with ignoring the issues and just pushing to CR. I also don't think any syntax change should be pushed to L4, because as sylvain says they need to be fixed now if at all. 17:41:40 fantasai - please don't strawman - no one is just pushing to CR 17:42:01 sylvaing: I don't think the process is blocking us here. 17:42:16 fantasai: If people want to cycle through mutliple LCs because they feel that somehow makes it better, fine 17:42:19 tantek: In practice it is rarely a few weeks from first LC to CR. 17:42:51 ChrisL: Often it takes way longer to process results. 17:43:09 tantek: How long a LC do you want, Sylvain? 17:43:27 tantek: So we have a proposal for, what, 8 weeks LC? 17:43:35 does that include time for processing? 8wks seems long for comment period 17:43:57 ChrisL: Seems like 8 weeks for dealing with issues, not actually the comment/review period. 17:44:04 3-4 weeks should be enough for comments... 17:44:13 sylvaing: I think 3 for review, 8 for dealing seems fine. 17:44:37 sylvaing: I think we can realistically take this to CR in 2-3 months. If we don't think it's doable, what are we doing dropping prefixes? 17:44:48 dbaron: I think that in some cases, the specs are in bad shape where impls interop. 17:45:01 dbaron: Not saying everything, but several cases where we have interop but the spec doesn't describe it properly. 17:45:04 smfr: Can you give an example. 17:45:07 dbaron: Not off my head. 17:45:16 tantek: When that happened in css2.1, we just changed the spec. 17:45:27 dbaron: I'm not even saying the spec is different, but rather that it's unclear. 17:45:36 glenn: And that should be fast. 17:45:55 s/glenn/glazou/ 17:45:56 (Though I'm thinking of some aspects of the model for animations.) 17:46:27 text-size-adjust is a good example of what dbaron just said 17:46:45 tantek: So, Sylvain, you want to drop prefixes in 11 weeks, not tomorrow, is that right? 17:46:49 sylvaing: I think so, yeah. 17:47:19 sylvaing: I don't want to make precedents for anything. 17:47:25 Ms2ger has joined #css 17:47:27 where is "unprefixing rule" documented? 17:47:41 http://www.w3.org/TR/CSS/ 17:47:58 tantek: No precedent, this is an exception. 17:48:06 glenn: the green text:http://www.w3.org/TR/CSS/#experimental 17:48:18 tnx 17:48:32 sylvaing: We ahve a spec with four impls, but there hasn't been an urgency. 17:49:12 hober: I think this is top priority 17:49:41 [more unminuted discussion, arggggg] 17:50:13 glazou: I suggest the 3 browser vendors that want to unprefix discuss amongst themselves. 17:50:36 q? 17:50:45 glazou: No consensus is emerging, despite all the discussion that has already happened. 17:50:51 glazou: We are *moving on*. 17:51:16 q+ 17:51:17 ack ChrisL 17:51:17 ChrisL: Since we don't have consensus on dropping prefixes, I think the chair should discuss moving LC forward. 17:51:22 glazou: Agreed. 17:51:30 [unminuted discussion consisted of Sylvain arguing for just going through with the process rather than making an exception, and others arguing for making the exception] 17:51:31 glazou: So what are we going to do to address the issue asap. 17:51:32 q- fan 17:51:45 smfr: It seems we need to split into 3 and 4, where the new SVG stuff goes into level 4. 17:51:52 smfr: With the remaining issue being 3d transforms. 17:52:19 [other unminuted discussion about daniel ruling that there is no consensus, and we should therefore dedicate our time to solving the issues and moving the spec forward] 17:52:21 tantek: I agree with smfr. I think that the problem here is not being properly understood. We'd like to implement unprefixed at the same time. 17:52:54 ack tantek 17:52:58 tantek: Let me make it clear. If the WG cannot unprefix quickly, we (firefox) will implement -webkit- prefixes. 17:53:18 Dirk: Because of level 3/4 splitting, I don't think it makes sense to do the SVG stuff in two levels. 17:53:38 Dirk: I don't think SVG is blocking 2d transforms, maybe 3d transforms. 17:53:54 wouldn't it be better to go to a common prefix rather than reimplementing vendor specific prefixes? e.g., instead of simply dropping rule, encourage all vendors to support -w3-wd-... or some such? 17:53:55 i understand webkit-only properties being an issue for mobile; transforms is not in that category imo 17:54:00 ChrisL: We know what the differences are between SVG and CSS transforms. 17:54:46 tantek: For transitions and animations, you do? 17:55:02 sylvaing: No, I don't think any of those are killer. 17:55:24 TabAtkins: sylvain, that's different from what you said at the f2f 17:55:30 sylvain: No, it's consistent. 17:55:41 Sylvain said that -webkit-was a problem. He did not say that transforms was a problem. 17:55:51 sylvaing: I don't think 3 months will make a difference. I want to prioritize and move on. 17:55:53 krit has joined #css 17:56:29 tantek: If the option is between -webkit- and unprefixed, or -webkit- and nothign else, I prefer the first option. But delaying unprefixed will not delay the decision we're making. 17:56:49 florianr: This seems USELESS to continue discussing, since this is not working here. 17:57:13 would prefer a common w3c sanctioned prefix over no prefix 17:57:13 I want to hear from everyone who voted (2), what issues do you see as blocking LC for those 3 specs? 17:57:14 glenn: Moz, MS, Opera, discuss together next week and bring a COMMON position to the WG. 17:57:19 s/glenn/glazou/ 17:57:34 glazou: If we end up with multiple positions in our call next week, this is a *waste of our time*. 17:57:41 glazou: So start that immediately in the mailing list. 17:57:48 glazou: tantek, can we try that? 17:58:15 glazou: Today we came for discussion, and I thought the 3 browser vendors had a common position. Apparently that's not the case. 17:58:34 glazou: So please get your positions together and bring it to the group, so we don't waste our time again. 17:58:39 tantek: I've put our position on the table. 17:58:45 tantek: I think the onus is on the objectors. 17:58:57 s/onus/burden 17:59:03 tantek: Anyone who objects, please bring reasons for why they're opposing unprefixing, or why they're opposing LC. 18:00:15 glazou: I suggest we adjourn on this failure status, and we work on the issues RIGHT NOW in the mailing list. 18:00:28 glazou: I can't declare any consuses with a 9-8 vote. 18:00:47 -[Microsoft] 18:00:49 -glenn 18:00:50 -antonp 18:00:51 -dbaron 18:00:53 -krit 18:00:54 -kojiishi 18:00:54 -[Apple.a] 18:00:55 antonp has left #css 18:00:56 -??P75 18:00:56 - +1.650.253.aadd 18:00:58 -Rossen 18:00:59 -[Apple] 18:01:01 -Bert 18:01:03 -tantek 18:01:05 -florianr 18:01:05 Zakim, who is on the phone? 18:01:07 On the phone I see glazou, stearns, plinss, nimbu, ChrisL, howcome 18:01:09 -howcome 18:01:11 -stearns 18:01:20 Zakim, who is on the phone? 18:01:21 On the phone I see glazou, plinss, nimbu, ChrisL 18:01:34 what I am out of phone 18:01:35 :/ 18:01:41 zakim, drop nimbu 18:01:43 nimbu is being disconnected 18:01:43 -nimbu 18:01:47 smfr has left #css 18:02:21 dbaron has joined #css 18:02:52 tantek: Yes, please. 18:02:56 Also: OMG 18:03:49 tantek: if it goes too slowly and you end up implementing -webkit-, will you drop -webkit- once the process finally gets to the unprefixing state? 18:03:54 ChrisL - no, the people that objected to (1) stopped that. 18:04:05 stearns - unknown 18:04:16 tantek: Then you needed another option: Publish LCWD now, don't drop prefixes until CR 18:04:23 fantasai - sure, if we have to publish multiple last calls, so be it. 18:04:44 no, we need to drop prefixes as part of the exception clause for the snapshot as part of this 18:05:12 tantek no. options 1 and 2 both involved moving to lcwd. the only difference was whether prefixes got dropped at lc or at cr 18:05:12 tantek: we spent the entire telecon arguing about that, and got no progress on moving to LC as a result 18:05:51 ChrisL - no such promise was made in 2 18:05:56 from IRC: 2) No exception, just try to move the specs fast 18:06:01 SteveZ has joined #css 18:06:20 tantek: see query 18:06:58 fantasai - I've never had much hope for telcon productivity in general, so unfortunately I'm not that surprised. 18:11:43 ChrisL - I'm still planning on asking to move Transforms, Transitions, Animations to LC ASAP. 18:11:50 regardless of prefix discussions 18:12:03 btw 18:12:34 Forgive me being a noob, but how does it help to move a spec to LC with known issues, if we don't drop prefixes as well? 18:12:48 howcome has left #css 18:12:52 florianr - it helps force resolution of issues more quickly 18:13:00 which then tends to remove objections to drop prefixes 18:13:28 -glazou 18:13:29 -ChrisL 18:13:33 -plinss 18:13:34 Style_CSS FP()12:00PM has ended 18:13:34 Attendees were glazou, Doug_Schepers, +1.206.550.aaaa, Bert, stearns, glenn, florianr, [Microsoft], hober, plinss, fantasai, [Apple], +93550aabb, danielweck, smfr, krit, 18:13:34 ... +1.415.871.aacc, antonp, +1.650.253.aadd, +1.206.552.aaee, tantek, dbaron, kojiishi, ChrisL, +47.21.65.aaff, howcome, nimbu, Rossen 18:13:53 tantek: That can be done with less process overhead by addressing issues at a high priority while implementing high-fidelity tracking 18:14:10 tantek: The advantage of LC is that it pushes people to report their issues 18:14:15 tantek: and review if they haven't yet 18:14:46 fantasai - in practice I don't believe that. In practice going to LC is what causes more quick reporting/addressing of issues. 18:14:51 tantek: The disadvantage is that when you make significant changes as a result of feedback, you have to recycle through LC, which imposes 3-week minimum 18:15:01 fine with going thru LC again 18:15:12 we already agreed it would take 8 weeks *after* LC 18:15:18 so that gives us 2 more LC cycles :P 18:15:23 heh 18:15:24 3 if we push to 9 weeks 18:15:32 <-- can do division 18:15:40 btw, LOTS of people have been complaining that the problem with the -webkit- prefixes being established / mobile web monoculture is that the CSSWG has not moved fast enough - e.g. @stubbornella. 18:15:52 today's telcon was clear support of that hypothesis 18:15:59 that it's the CSSWG's fault for moving too slowly. 18:16:21 tantek: There were multiple telecons last December where daniel cancelled or closed early because nobody brought any issues forward for WG resolution 18:16:32 tantek: Transforms issues could have been addressed during that time 18:16:37 tantek: Why were they not addressed? 18:16:44 because it wasn't in LC 18:16:48 LC forces the resolutions 18:16:59 tantek: s/CSSWG/a few members/ 18:17:01 please 18:17:02 tantek: No it doesn't, the editor bringing up the issues to the WG does. 18:17:07 glazou - that's not what people see 18:17:13 uuuuh ????? 18:17:13 they see lack of consensus 18:17:17 and 18:17:18 ? 18:17:18 they see process 18:17:22 etc. 18:17:27 we should be dictators ??? 18:17:28 tantek: If the spec is in LC, and the editor is MIA, nothing moves. 18:17:28 they see objection without providing reasons 18:17:31 I'll have to side with fantasai here 18:17:39 tantek: Same as if the spec is in WD, and the editor is MIA, nothing moves. 18:17:40 fantasai - I'm working on that editor MIA aspect 18:18:11 Missing In Action 18:18:13 Missing iIn Action 18:18:57 In the last 9 months I do not recall any Transforms issues being addressed by the CSSWG except at F2Fs. 18:19:48 nobody ever brought that as agenda item 18:19:49 ever 18:19:51 How can you make fast progress with that? 18:19:54 and we kept asking 18:19:56 Exactly. 18:20:04 so seen from peter and I, it was NOT urgent 18:20:18 we have no brain scanners 18:20:25 we deal with what we see 18:20:30 and the requests we get 18:20:49 so I am _extremely_ upset and depressed to read some considered it's WG fault 18:20:51 it is NOT 18:20:56 name the guilty ones: MEMBERS 18:21:11 we do what the MEMBERS want here 18:21:16 always 18:21:31 anyway, I have to go 18:21:37 Here is a (perhaps naive) proposal. The chairs should make sure to nag members until each document that has reach FPWD or later has at least two editors from a different member 18:21:39 hope my kids will be in better shape than this WG 18:21:41 bye 18:21:49 just a second glazou 18:21:54 not more 18:21:58 what do you think of what I said above 18:22:14 in theory, nice ; in practice that's another story 18:22:23 members DO resist to such proposals 18:22:31 and that's not WG's responsibility but theirs 18:22:46 right 18:22:50 of course not 18:22:55 or an editor that disappears during six months 18:22:59 or more 18:23:07 nothing the chairs can do there 18:23:16 if the members don't jump on it 18:23:18 but it might be nice to point it out as a risk to progress when a spec's editor list is insufficiently diverse 18:23:24 if that's urgent, they should act ! 18:23:41 I really need to go, and I killed my evening enough for today 18:23:42 bye 18:23:47 bye 18:25:33 fantasai: in the last 9 months many transforms bugs have been resolved in bugzilla & the spec. so i'm not sure what you mean when you say that that's only happened at f2fs 18:27:33 i think fantasai means it doesnt get discussed in teleconfs 18:27:39 yeah 18:31:15 it doesn't need to get discussed in telecons to make progress 18:31:18 things can happen via email 18:31:41 it gives group members a distorted image of where progress is being made, though 18:31:53 but if there are issues blocked on WG resolution, they should be brought up 18:32:08 and if there are issues being resolved and changes being made, there should be Working Drafts published 18:32:42 that both keeps the /TR page up-to-date, but also functions as a check point 18:33:06 if that were as easy as pressing a button, fine 18:33:26 but, frankly, it's not, so it takes time away from actually addressing issues 18:33:59 It almost is: just ask for a decision to publish in the WG and then I'll do the rest... 18:55:21 editors being MIA is a good reason to allow forking specs 18:55:43 Bert - getting the WG to agreed to the decision to publish is the problem 18:55:56 we couldn't even agree to take 3 relatively stable drafts to LC 18:56:05 despite sense of urgency etc. 18:56:32 actually, HTMLWG has it better in this way 18:56:46 they automatically publish latest editor's drafts as heartbeat TR WDs 18:57:00 unless there is a specific objection 18:57:08 so in practice, people being MIA or unresponsive don't block TR WD publication 18:57:09 tantek, well yes, because they can't get consensus on anything but editorial issues 18:57:10 tantek: LC is different than WD 18:57:16 perhaps we should switch to that model for CSSWG 18:57:27 tantek: WD would get few, if any, objections 18:57:28 so that at least our public WDs wouldn't get 2+ years out of date :( 18:57:34 tantek: LC implies that all issues are resolved, and we know they're not 18:58:05 tantek: that's probably a good idea. Right now we rely on editor's to request publication, and they often dont. 18:58:14 tantek: btw, you're one of those 18:58:15 :) 18:58:15 fantasai, http://www.w3.org/TR/css3-animations/ is almost 3 years old. http://dev.w3.org/csswg/css3-animations/ was updated last week. 18:58:27 tantek: I *know* 18:58:28 that's the problem I'm talking about 18:58:42 HTMLWG heartbeat publishing of WDs is better in that regard 18:58:47 we should just adopt that in the WG 18:58:50 CSSWG 18:59:04 tantek: Makes less sense for us because we have so many specs 18:59:08 no 18:59:13 makes *more* sense 18:59:17 tantek: Publishing eveyrthing that hasn't changed is not useful 18:59:24 too easy to miss a neglected spec 18:59:26 Someone could write an app to compare the last update of TR and ED specs, and send email to css-wg once the difference is more than three months 18:59:30 fantasai - they HAVE changed 18:59:32 that's the problem 18:59:34 in the editor's draft 18:59:35 duh 18:59:52 Ms2ger - or we could make the chairs do it 18:59:52 tantek: YES, we should publish THE ONES THAT HAVE CHANGED, but not EVERYTHING 18:59:56 the way the HTMLWG chairs do it 19:00:13 fantasai - why bother with the difference? 19:00:18 why are you making extra work? 19:00:25 tantek: because people rely on the date to know when the draft was last updated 19:00:27 just publish updates for all of them 19:00:42 tantek: No, I refuse to agree with you. 19:00:42 so they do for the editor's draft as well 19:00:53 all that's happened is that TR has become irrelevant 19:00:56 and people implemented ED now 19:01:04 so you can either ignore that and be ok 19:01:06 with it 19:01:09 or try to salvage TR 19:01:13 *sigh* 19:01:17 you're ridiculous 19:01:23 and I am not discussing this anymore with you 19:01:28 and with ad hominem I'm outta here 19:01:31 try again tomorrow. 19:01:50 but I am going to dinner now 19:01:58 Heh 19:02:05 Enjoy dinner 19:20:32 krijnh has joined #css 19:22:58 SteveZ has joined #css 19:24:05 drublic has joined #css 19:28:29 SteveZ has joined #css 19:29:31 SteveZ has joined #css 19:46:58 plinss: I love you. 19:47:07 :-) 19:53:29 SteveZ has joined #css 20:03:31 tantek_ has joined #css 20:05:47 SteveZ has joined #css 20:08:48 plinss: I love your gavel 20:09:12 THAT IS NOT A EUPHAMISM!!!! 20:09:22 an euphamism? 20:10:47 It's spelled "stephen". 20:13:08 krit has joined #css 20:15:26 Zakim has left #css 20:33:53 SteveZ has joined #css 20:36:54 SteveZ has joined #css 20:45:41 tpod has joined #css 20:48:34 Plinss that video was pretty funny. And I've never watched The Wire either. 20:49:14 BTW I've created issues pages for transforms, transitions, and animations on our wiki. 20:49:48 We've got those in bugzilla 20:56:49 tpod: you are missing something really really amazing 20:57:18 i may not evangelise html5 but I will evangelize The Wire 20:58:53 SteveZ has joined #css 20:59:42 The Wire is effing awesome 21:01:06 glenn has joined #css 21:04:39 thirding on the Wire. Probably the best series ever broadcast on TV. 21:09:30 agreed 21:12:08 jet has joined #CSS 21:13:57 SteveZ_ has joined #css 21:15:25 The Sopranos is also up there 21:16:38 though the David Simon miniseries that preceded The Wire was pretty darn good too 21:27:58 dbaron has joined #css 21:43:15 SteveZ has joined #css 21:51:28 jet has joined #CSS 22:06:47 tpod has joined #css 22:14:36 tpod_ has joined #css 22:16:52 miketaylr has joined #css 22:40:16 karl has joined #CSS 22:46:29 krit has joined #css 22:49:33 myakura has joined #css 22:52:20 SteveZ has joined #css 23:07:55 SteveZ_ has joined #css 23:09:39 SteveZ_ has joined #css 23:11:38 florian has joined #css 23:20:32 krit has joined #css 23:35:16 SteveZ has joined #css 23:50:28 SteveZ has joined #css