16:24:52 RRSAgent has joined #css 16:24:52 logging to http://www.w3.org/2014/01/08-css-irc 16:24:57 RRSAgent, make logs public 16:27:37 eliezerb_2nd has joined #css 16:27:38 zcorpan has joined #css 16:28:26 glazou has changed the topic to: http://lists.w3.org/Archives/Public/www-style/2014Jan/0067.html 16:30:41 zcorpan has joined #css 16:33:31 zcorpan has joined #css 16:33:36 jet has joined #css 16:43:09 glazou: is there some approval for publishing CR? 16:43:35 eliezerb has joined #css 16:43:36 teoli_ has joined #css 16:43:36 in addition to the WG’s 16:44:19 ChrisL has joined #css 16:45:13 yes 16:45:22 there is a transition call with the Director 16:45:31 co-chairs + plh + Director's deputy 16:45:36 + Bert 16:45:50 hi ChrisL 16:46:13 hi glazou, happy new year 16:46:20 you too ChrisL ! 16:46:30 SimonSapin, see an example of a transition request at https://lists.w3.org/Archives/Member/chairs/2013JulSep/0040.html 16:48:22 also look here http://services.w3.org/xslt?xmlfile=http://www.w3.org/2005/08/01-transitions.html&xslfile=http://www.w3.org/2005/08/transitions.xsl 16:48:36 and set the drop down to the appropriate stage 16:49:04 http://dev.w3.org/csswg/biblio.ref points to old drafts :( eg. CSS3CASCADE 16:49:34 its in a version control system, feel free to edit it 16:50:00 I will, but this really should be automatic 16:50:19 someone should rally implement that 16:50:26 s/rally/really 16:50:41 action: someone to do good stuff 16:50:41 Error finding 'someone'. You can review and register nicknames at . 16:50:45 I guess that’s Bikeshed bug #86 https://github.com/tabatkins/bikeshed/issues/86 16:52:02 yes 16:52:07 bugzilla.bluegriffon.org 16:52:10 ty 16:52:22 and a forum here : http://groups.google.com/group/bluegriffon 16:53:08 dael has joined #css 16:54:11 absolutely :-) 16:55:51 +1 for paste! 16:56:34 :) 16:56:50 we're about to start here anyway 16:56:52 Style_CSS FP()12:00PM has now started 16:56:59 +dael 16:57:16 +??P15 16:57:23 Zakim, ..P15 is me 16:57:23 sorry, glazou, I do not recognize a party named '..P15' 16:57:29 Zakim, ??P15 is me 16:57:29 +glazou; got it 16:58:12 antonp has joined #css 16:58:20 jerenkrantz has joined #css 16:58:25 leif has joined #css 16:58:33 scribenick: dael 16:58:50 +krit 16:58:59 +ChrisL 16:59:09 +dauwhe 16:59:28 +??P25 16:59:36 Zakim, ??P25 is me 16:59:37 +leif; got it 17:00:03 +[Bloomberg] 17:00:16 Zakim, Bloomberg has me 17:00:16 +jerenkrantz; got it 17:00:17 +Stearns 17:00:57 +[Bloomberg.a] 17:01:17 smfr has joined #css 17:01:29 + +37684aaaa 17:01:29 +??P38 17:01:34 florian has joined #css 17:01:36 Zakim, aaaa is me 17:01:36 +antonp; got it 17:01:38 Zakim, ??P38 is me 17:01:38 +SimonSapin; got it 17:01:48 +fantasai 17:01:57 +Bert 17:02:20 +Plh 17:02:30 +smfr 17:02:37 +[IPcaller] 17:02:56 Zakim, [IPcaller] has florian 17:02:56 +florian; got it 17:03:00 Zakim, [IPcaller has me] 17:03:00 +me]; got it 17:03:01 arybka has joined #css 17:03:02 Zakim, who is noisy? 17:03:13 glazou, listening for 10 seconds I heard sound from the following: [IPcaller] (1%), [Bloomberg.a] (9%) 17:03:20 Zakim, [Bloomberg.a] has arybka 17:03:21 +arybka; got it 17:03:21 +??P9 17:04:00 Zakim, ??P9 is rossen 17:04:01 +rossen; got it 17:04:16 +glenn 17:04:21 glazou: Extra items? 17:04:36 Topic: Seattle F2F and TTWF 17:04:49 glazou: Is sylvaing here? 17:05:08 glazou: So sylvaing sent a message about updating wiki w/ flight and diet 17:05:13 JohnJansen has joined #CSS 17:05:19 ...: He also says we'll have own name and password 17:05:26 ...: Please update wiki asap 17:05:40 ???: I don't have anything. Sunday before we have TTWF 17:05:46 ...: I encourage everyone to sign up 17:05:54 http://wiki.csswg.org/planning/seattle-2014#participants 17:05:56 s/???/stearns 17:05:59 ...: If you can't make it, send in test you need written so we have tasks 17:06:11 glazou: We also need to fill wiki with adjenda 17:06:22 ...: F2F is soon, so we need proposals 17:06:30 dbaron has joined #css 17:06:38 ...: plinss will review ASAP, but he's in London 17:06:40 +SGalineau 17:06:40 -SGalineau 17:06:42 ...: Anything else? 17:07:00 +dbaron 17:07:03 glazou: is sylvaing there? 17:07:10 +SGalineau 17:07:25 glazou: sylvaing, hello! 17:07:42 ...: We were about to clsoe Seattle F@F. Anything becides e-mail? 17:07:43 Woo, coming! 17:07:56 sylvaing: No. One new piece is a meetup WEdnesday night with local community 17:08:08 ...: If there's any comments on that, let us know. 17:08:20 glazou: Okay. WE may be leaving Wed night. 17:08:33 astearns: THere's not easy time. WE can check if Monday works. 17:08:38 glazou: Lets move on 17:08:42 Topic: Charter 17:08:44 s/astearns/sylvaing/ 17:08:54 glazou: We need an update on the charter extension 17:09:01 plh: I was contacted recently. 17:09:14 + +1.281.305.aabb 17:09:15 ...: It's going to review inside W3C and we'll have feedback by F2F 17:09:16 -rossen 17:09:22 sgalineau has joined #css 17:09:28 ...: If not feedback, we can continue with dicussion within the group. 17:09:42 ...: Hopefully we should be able to send for final review week after F2F or during it 17:10:06 ...: I do know that a draft hasn't done anything, but I do expect some feedback. I think it's as good as we can. 17:10:17 glazou: There's an arguement. WE're expecting progress on super group front. 17:10:27 ...: THat will allow us to make a different charter in 6 months. 17:10:33 plh: Right now end is Feb 2015 17:10:38 teoli has joined #css 17:10:41 ...: So 12 months. 17:10:46 ...: I guess that's fine. 17:10:50 ...: That makes sense. 17:10:53 That is fine, we can always recharter before it expires 17:11:03 glazou: That will let us with web consortioum discuss super group 17:11:14 plh: That's where we are 17:11:17 +??P31 17:11:19 glazou: Questions, comments? 17:11:32 Topic: CSS Fragmentation 17:11:38 https://lists.w3.org/Archives/Member/w3c-css-wg/2014JanMar/0009.html 17:11:40 glazou: WE have request from krit 17:11:49 krit: I create an ex with bordor radius 17:12:02 ...: Frag means I had multi column with an element across mulit. 17:12:10 ...: Question is how do we define diff frag. 17:12:27 +Lea 17:12:28 ...: Spec isn't clear if it's one box split into different parts or drawn between columns 17:12:38 ...: I think it's essential for many parts to define. 17:12:48 ...: DO we create diffenet boxes on frag? 17:12:53 rossen: Yes. 17:13:09 ...: I've been reading your comments and we can consider that every frag is a box and has its own model. 17:13:26 ...: The way border is controlled on break is done by using the border box decoration prop 17:13:36 ...: That gives you ability to have or donn't have padding on break 17:13:57 ...: So, to further elaborate, as to if that is one box in on frag, I think that's not correct 17:14:16 ...: Correct is this is collection of boxes. Frag flow is the collection, not multi fragments. 17:14:26 krit: To be clear, I'd like a resolution to document 17:14:42 rossen What type of resoultuon? One to have us edit spec is fine. 17:14:59 krit: I just want res that each fragment creates own box. 17:15:02 +SteveZ 17:15:03 rossen: Yes. 17:15:14 fantasai: The entire point of fragment is to distinguish from box. 17:15:27 krit: That's fine as long as spec that each frag has own piece. 17:15:48 dbaron: There's a bunch of existing specs that assume one or the other. MOstly assume each frag is own box 17:16:05 ...: I'm fine either way, but resolution needs to say it's not changing existing specs and they might disagree. 17:16:09 rossen: I'm with you. 17:16:22 +??P73 17:16:30 Zakim, I am ??P73 17:16:30 +leif; got it 17:16:31 ...: I think that first it being closer to CSS 2.1 for line boxes and the fact they are boxes is that right way to go 17:16:42 roseen: So should we have resolution. 17:16:46 s/line boxes/inline boxes/ 17:16:52 fantasai: I think that's dependant on us for frag. 17:16:57 krit: I think it's every spec. 17:17:12 Rossen: WE can see what references and see if there are differences. 17:17:25 ...: I can't think of anything but multi column, box, and page that talk about this. 17:17:32 ...: For those I think they're only talking boxes. 17:17:47 ???: WE also have box generation where they don't have size or position 17:17:56 s/???/SimonSapin 17:17:58 fantasai: What do we call it. Full name is box fragment. 17:18:09 ...: The CSS 2.1 calls them both box 17:18:19 ...: THe content is a box, it gets split, and it's both box. 17:18:30 ...: So we need to call them box, but be able to distinguish 17:18:45 rossen: This is why we used frag. to distinguish. Is that the confusing part? 17:18:55 fantasai: We also mix us element and box on generation side 17:19:17 krit: If fragment is how it differs? When a frag has its own padding isn't defined. 17:19:29 fantasai: Maybe box fragmenet and box element and they can go by all those names? 17:19:38 SimonSapin: I think it is defined 17:19:46 rossen: That's what I was saying a few minutes ago 17:19:47 We can call them both boxes, or we can call the fragments / elements 17:19:51 s/the/them/ 17:19:56 -glazou 17:20:01 s/defined/defined by the box-decoration-break property/ 17:20:07 +??P15 17:20:10 Zakim, ??P15 is me 17:20:10 +glazou; got it 17:20:12 krit: It's not clear which box you mean 17:20:21 rossen: WE mean fragmenet box, but we can be clear 17:20:38 fantasai: In frag spec we use frag when we mean it and box when we mean box for the most part 17:20:52 glazou: What is the action for the near term? 17:20:57 -[IPcaller] 17:21:06 smfr has left #css 17:21:10 fantasai: We need a set of terms to agree first. I propose box-element and box-fragmenent 17:21:14 smfr has joined #css 17:21:17 dbaron: I don't like box-element 17:21:33 me neither 17:21:37 let's rename this at CR anyway 17:21:41 fantasai: Problem is we have a lot that use box and use term element. We need a term for box-element things that can be shortened to box or element. 17:21:54 dbaron: I think that if it's element and isn't an element in the dom it's wrong 17:22:03 rossen: can we have element-box and frag-box instead? 17:22:12 krit: I like element-box 17:22:18 s/(above)/I think specs that use the term "element" to refer to something other than an element in the DOM are wrong and should be fixed./ 17:22:20 SimonSapin: I'm fine with box-frag. 17:22:20 +1 to dbaron - should not propagate the problem of conflating boxes with elements 17:22:32 s/SimonSapin:/???:/ 17:22:34 I like frag-box. Anything with 'element' in there implies its in the DOM as a node 17:22:37 rossen: we can easily clarify in box decoration 17:22:43 krit that's what I said. 17:22:47 agree with ChrisL 17:22:57 fantasai: fragmenet means the element and it's consistant on that 17:23:10 rossen I think what krit was saying is he's confused about fragmenet boxes 17:23:21 fantasai: We were going now,, fragmenets are not peices of the block. 17:23:39 rossen: That' wasn't my intention. The way we impl is the opposite 17:23:48 s/fragmenet means the element/box is the generated abstract thing, and fragment is the piece of it/ 17:23:52 ...: There could have been mis communication, but I've always thought of them as boes. 17:23:59 sgalineau, that's exactly right 17:24:02 krit: There's a difference. Webkit is one box. 17:24:12 ...: IE and Firefox does diff boxes. 17:24:18 rossen: Becuase we impl frag. 17:24:38 fantasai: Firefox has frames into a chain which rep box and each frame is a fragment 17:24:41 fantasai: so they're box fragments. but the terminology does not answer whether border/padding/margins get duplicated on fragments or not 17:24:49 eliezerb has joined #css 17:24:56 krit: So in this case you're saying the frag is right? 17:25:03 glazou: We need to move one. Can we con't on ML? 17:25:05 sgalineau, that’s box-decoration-break 17:25:07 rossen: Yes 17:25:10 sgalineau: Isn't that what box-decoration-break is about? 17:25:13 glazou: I think that's better. 17:25:33 glazou: We see the problem and we should have margins etc on the fragement, but how to say it tin the spec is undefined 17:25:44 Topic: Shapes LC 17:25:45 https://lists.w3.org/Archives/Member/w3c-css-wg/2014JanMar/0014.html 17:25:47 sgalineau, haa, naming :) 17:25:59 fantasai, ok 17:26:02 http://dev.w3.org/csswg/css-shapes/issues-lc-20131203.html 17:26:03 astearns: WE're at the end of the comment period 17:26:08 MaRakow has joined #CSS 17:26:10 -leif.a 17:26:12 ...: I've gone through all and created a disposition. 17:26:17 pointer to dispo of comments? 17:26:25 ...: got comments from divpub and posted to www-style. 17:26:34 ...: Nothing formal from SVG, but got from TabAtkins and krit 17:26:37 s/divpub/digipub/ 17:26:37 http://dev.w3.org/csswg/css-shapes/#20131203 17:26:46 ...: There were some explinations and clarifications. 17:27:05 SimonSapin: SVG was also TabAtkins and he said we didn't have shape from before. 17:27:16 astearns: He said that before LC so it's not LC 17:27:22 ChrisL: Did he agree? 17:27:23 s/SimonSapin:/???:/ 17:27:45 s/divpub/digipub/ 17:27:45 astearns: I gave him rational, but I don't remember what he said. 17:27:45 s/TabAtkins/Tavmjong/ 17:28:14 astearns: Some sub changes. I added serialization and I changed outside from auto-none and I assume we need 2nd LC 17:28:27 ...: I want to wait until serialization of background is decided. 17:28:36 ...: Background position changed and I had to adapt 17:28:46 ...: I wanted to make sure they're serializing in the same way. 17:28:59 ChrisL: I want to make sure tav's comment is addressed. 17:29:12 ...: They did in good faith impl something we did and then we backed away 17:29:25 ...: They need to put text in shapes and they're trying to do what CSS is doing. 17:29:33 ...: They need to have something they can use. 17:29:47 ...: Even though it was raised before LC, I'd encourage you to ensure he's okay. 17:29:53 astearns: I'll get back to him on that issue. 17:30:04 -??P31 17:30:08 +[Microsoft] 17:30:09 +??P11 17:30:18 rossen____ has joined #css 17:30:18 ...: My position from last time is, just because shape inside isn't in lvl 1 doesn't mean we can't go ahead with impl if it's a lvl 2 feature. 17:30:24 Zakim, I am ??P11 17:30:24 +leif; got it 17:30:41 zakim, microsoft has me 17:30:41 +rossen____; got it 17:30:41 ...: If it's a lvl 2 feature, they can do it. WE also have it in webkit and blink and it's just postoned on impl side. 17:30:47 glazou: I have a question on issue 6 17:31:02 glazou: ?? said does this okay with svg WG. 17:31:08 astearns: We didn't get an answer. 17:31:21 astearns: We should get a positive responce, but we do need it. 17:31:48 ChrisL: One useful way forward is to e-mail them and say we need to know if you have comments or need more time 17:31:53 astearns: I will do that today 17:32:04 astearns: That's all I had. I just wanted to update group 17:32:13 Topic: CSS Syntax CR 17:32:14 http://lists.w3.org/Archives/Public/www-style/2014Jan/0060.html 17:32:14 http://lists.w3.org/Archives/Public/www-style/2014Jan/0060.html 17:32:27 SimonSapin: I did not recieve any comments since we discussed. 17:32:43 ...: I happen to have found something online that I tried to address with mostly editorial clarification 17:32:50 ...: No normative changes for impl 17:32:58 ...: This is comments from ITN WG 17:33:16 s/?? said does this okay with svg WG/our response asked whether this was OK with i18n/ 17:33:16 ...: So I don't know if I should wait for them or what's the next step 17:33:27 s/ITN/I18N/ 17:33:33 glazou: The LC period ended three weeks ago so we're beyond limit 17:33:43 fantasai: Internationalization did way they might be late. 17:33:50 SimonSapin: Didn't tell me 17:33:58 glazou: It's becoming urgent 17:34:14 fantasai: I would ping Richard ? and ask him if he has comments or need time 17:34:30 SimonSapin: I did include int. yesterday. Should I ask Richard specifically. 17:34:44 fantasai: I would do that and give him time to respond. Their cycles are slower. 17:34:51 ...: You should get responce this week. 17:35:11 ...: I'm happy to say we can resolve for CR as long as they're happy, but I'd like them to say they're okay. 17:35:14 SimonSapin: Okay 17:35:20 SimonSapin: I'm happy to reach out 17:35:43 glazou: I'm in principal okay with that. One point, setting a deadline and never ever meeting it is pointless. 17:35:44 (Richard is on vacation this week.) 17:35:52 glazou: Four weeks beyond is a lot. 17:36:14 ...: I'm not saying anyone is guilty, but we have a process. We can extend when people are going to take more time. 17:36:27 ...: And we can be firmer on the limits, or there's no point in a review period. 17:36:28 they should ask for an extension. And its asking: we can say no 17:36:38 fantasai: He did say he's busy and would be taking seveal weeks off. 17:36:49 ...: Also, this isn't urgent to put in CR. No one is waiting for it. 17:36:59 glazou: I agree. Remember, I said in principal. 17:37:08 SimonSapin: He told you, but he should have told the WG 17:37:12 fantasai: He should have. 17:37:25 glazou: When you contact them, I want you to be firm with them on time. 17:37:34 glazou, the change you made just made the sound worse 17:37:38 glazou, your audio is completely saturated 17:37:38 emalasky has joined #css 17:37:42 daniel we can't hear you at all well, lots of distortion 17:38:11 glazou: I said that I want to be sure that SimonSapin is okay with plan to ask for somments and get extension. 17:38:19 glazou: If you're not ok we'll decide. 17:38:24 SimonSapin: I'm fine with waiting. 17:38:34 glazou: Please Ping Richard ASAP 17:38:51 ...: What I see is only editorial changes, so it's easy to move to CR if WG agrees. 17:39:00 ...: Shall we defer to next week? 17:39:04 http://lists.w3.org/Archives/Public/www-style/2013Dec/0403.htmlhttp://lists.w3.org/Archives/Public/www-style/2013Dec/0403.html 17:39:12 SimonSapin: Well, we already resolved. 17:39:21 glazou: We're waiting for comments. 17:39:31 fantasai: We have that if internationalization agrees we can resolve. 17:39:42 glazou: Be we don't have a resolution on these comments. 17:39:47 SimonSapin: So we'll tlk next week 17:39:50 glazou: That is better. 17:40:00 lmcliste_ has joined #css 17:40:05 ...: If Richard answers no comments then we're fine and we can move one. 17:40:12 SimonSapin: What is the next step for CR 17:40:27 glazou: Bert will issue transition request and we'll have a call with a director? 17:40:38 ChrisL: Did you see the link I posted with the specs for CR 17:40:47 SimonSapin: My question was more what do I need to do 17:41:04 ChrisL: As long as your dispoition of comments is in order, you don't need anything else. 17:41:11 glazou: So you're all set. 17:41:17 Topic: Fragmentation 17:41:41 fantasai: I wanted to, before we untangle box fragments that would require sig changes, I was wondering about pub and updated WD. 17:41:52 ...: if people think that's a good idea. 17:42:03 florian has joined #css 17:42:04 ???: You asked me to review and I posted stuff on the 6ths of Dec. 17:42:06 Zakim, mute me 17:42:06 glazou should now be muted 17:42:12 fantasai: I'm happy to go through those. 17:42:15 s/???/astearns 17:42:16 +??P76 17:42:25 ...: I'll try this week and ask for a WD next week. 17:42:39 ...: I'm also holding us boxes and borders b/c I wanted to pub both together. 17:42:42 Zakim, unmute me 17:42:42 glazou should no longer be muted 17:42:44 s/us/up/ 17:42:47 tantek has joined #css 17:43:02 Zakim, mute me 17:43:02 glazou should now be muted 17:43:02 astearns: on backgrounds and borders I want cerealization defined before we publish. 17:43:13 fantasai: Is it in OM? It's not in B&B level 3 17:43:15 s/cerealization/serialization/ 17:43:34 astearns: You and TabAtkins were taling and said you need to make sure serialization is correct 17:43:34 Zakim, unmute me 17:43:34 glazou should no longer be muted 17:43:45 fantasai: It's somewhat defined but may be confusing 17:43:55 glazou: Any other items? 17:43:56 Zakim, +??P76 is tantek 17:43:56 sorry, tantek, I do not recognize a party named '+??P76' 17:44:04 Zakim, ??P76 is tantek 17:44:04 +tantek; got it 17:44:11 glazou: I guess this is a shorter call 17:44:21 +1 to the generated content should be actual content please 17:44:22 Zakim, mute me 17:44:22 glazou should now be muted 17:44:25 leaverou +1 17:44:32 ??: I wanted to ask about images. I fwe want live images for CSS image 17:44:37 sliced-image() function 17:44:38 s/???:krit 17:44:41 s/???/krit 17:44:49 ...: Where we have border images and if we can have something liket hat for CSS images 17:44:49 leaverou, Bikeshed’s issue index helps, though 17:44:49 http://lists.w3.org/Archives/Public/www-style/2014Jan/0000.html 17:44:56 ...: I can link the proposal 17:45:10 Zakim, unmute me 17:45:10 glazou should no longer be muted 17:45:13 SimonSapin: ah, good point, I forgot about that 17:45:20 ...: The intention of the report is that we remove the box propeties that do for masking the same as border image. 17:45:36 ...: If we use border image to avoid another property. 17:45:53 ...: I want to ask the group if it makes sense to have a sliced image and if I should move forward. 17:45:56 you too tantek 17:46:08 fantasai: A sliced image is fine, but anything within the image would be tricky. 17:46:15 ???: You'd have to do an outset. 17:46:32 fantasai: I'm not convinced. Maybe 9-slice images it useful for other things, but not for border and masking. 17:46:35 s/???/ChrisL 17:46:48 fantasai: b/c those perameters and being about to tie to the border width 17:47:07 ChrisL: This would move the complicated slicing numbers into imge which would simplify border image 17:47:15 fantasai: I'm not sure how you mean 17:47:16 s/ChrisL/smfr 17:47:37 smfr: If this is like masking and broder image, I don't thinkt hat's tied to the 9-piece-ness of the image. 17:47:46 smfr: Are they tied to slice width? 17:47:59 fantasai: Tied to how we define the outside of the box. 17:48:06 fantasai: You'd have one big image yous tretch 17:48:15 smfr: So the assets are seperate from 9 17:48:24 smfr: I think this would be useful 17:48:28 smfr: the outsets are independent of the 9-sliced-ness of the image 17:48:31 fantasai: What else would you use it for. 17:48:34 s/assets/outsets/ 17:48:36 smfr: The buttons. 17:48:45 fantasai: Wouldn't you use border imge for that? 17:48:55 smfr: I htink masking is a concrete use-case 17:49:16 krit: For border image I don't think it's a problem, though may not make it easier. It's another way to do it. 17:49:30 Zakim, mute me 17:49:30 glazou should now be muted 17:49:31 fantasai: One reason we split border image is people wanted to take small pieces out. 17:49:41 ...: This made it easier to change one piece. 17:49:48 smfr: That's fine. 17:50:02 fantasai: That doesn't apply to masking, but you wouldn't want to change on have. 17:50:12 tantek: I think background use case is simplier. 17:50:35 ...: That way you don't have to use border height to alter. Not a big advantage, but simplier to achieve end result. 17:50:42 fantasai: You'd still need same prop. 17:50:44 -[Bloomberg] 17:50:59 tantek: It's less work slightly on metrics pieces, which is the harder piece to get right. 17:51:12 Zakim, unmute me 17:51:12 glazou should no longer be muted 17:51:22 glazou: So, krit, anything else on this? 17:51:31 Zakim, mute me 17:51:31 glazou should now be muted 17:51:31 krit: My intention was to have match box. 17:51:46 ...: I'd like to emphasis even with proposals I'd still like to have mask-box 17:51:48 s/match box/mask box 17:51:52 fantasai: I think it makes sense. 17:52:13 krit: So smfr should we proceed with this image prop to replace mask box? 17:52:28 smfr: I thinkit would be useful to solicit use-cases to see if it would be useful. 17:52:44 krit: That's independant of mask image 17:52:58 ...: So do we want mask box or proceed with replacing it with mask image 17:53:05 smfr: I don't know if I can make that call now 17:53:12 krit: I'm fine with waiting, but how long? 17:53:22 smfr: If we do this, it would be images 4, right? 17:53:31 Zakim, unmute me 17:53:31 glazou should no longer be muted 17:53:38 fantasai: We have F2F coming up. This could be on the adjenda to wrap this up. 17:53:44 smfr: That's resonable. 17:53:49 krit: Aboslutely. 17:53:51 -dbaron 17:53:52 glazou: Anything else? 17:54:01 Zakim, unmute me 17:54:01 glazou was not muted, glazou 17:54:05 whoa 17:54:07 not me 17:54:11 Zakim, mute me 17:54:15 glazou should now be muted 17:54:21 ROFL 17:54:29 :) 17:54:35 ROFL tab 17:54:36 Zakim, unmute me 17:54:36 glazou should no longer be muted 17:54:40 ??: How about June dates? 17:54:51 glazou: I was away for last 10 days and couldn't ping Samsung. 17:54:59 ...: I'll do that now and report ASAP. 17:55:04 Huge +1 for Korea meeting. 17:55:07 s/??/SteveZ/ 17:55:14 stevez: You're away that AC meeting is 8-10? 17:55:30 glazou: Plan is to have it in Seoul, not Samsung HQ because we'd have netowrk issues. 17:55:37 glazou: I'll report as soon as I can. 17:55:45 glazou: I guess that's all for today 17:55:53 -Plh 17:55:54 -SGalineau 17:55:55 -smfr 17:55:56 glazou: Talk to you next week! Bye! 17:55:57 -antonp 17:55:58 -fantasai 17:55:58 -[Microsoft] 17:55:59 -Stearns 17:55:59 -dauwhe 17:56:00 -SimonSapin 17:56:00 -ChrisL 17:56:01 -Lea 17:56:01 -glazou 17:56:02 -tantek 17:56:02 -krit 17:56:03 -SteveZ 17:56:04 -dael 17:56:05 -Bert 17:56:05 -leif.a 17:56:06 -TabAtkins 17:56:11 -glenn 17:56:22 -[Bloomberg.a] 17:56:23 smfr has left #css 18:05:01 disconnecting the lone participant, leif, in Style_CSS FP()12:00PM 18:05:02 Style_CSS FP()12:00PM has ended 18:05:02 Attendees were dael, glazou, krit, ChrisL, dauwhe, leif, jerenkrantz, Stearns, [Bloomberg], +37684aaaa, antonp, SimonSapin, fantasai, Bert, Plh, smfr, florian, me], arybka, rossen, 18:05:03 ... glenn, SGalineau, dbaron, +1.281.305.aabb, TabAtkins, Lea, SteveZ, rossen____, tantek 18:06:29 leif has left #css 20:00:50 zcorpan has joined #css 20:01:03 jet has joined #css 20:07:02 Zakim has left #css 20:08:30 dbaron has joined #css 20:36:24 zcorpan_ has joined #css 20:45:21 plh3 has joined #css 20:57:51 zcorpan has joined #css 21:01:47 jet has joined #css 21:18:51 dbaron has joined #css 21:18:54 zcorpan has joined #css 21:30:01 dbaron has joined #css 21:35:04 eliezerb_2nd has joined #css 21:51:20 jet has joined #css 22:00:06 jcraig has joined #css 22:23:20 jet has joined #css 22:36:27 jet has joined #css 22:39:50 zcorpan has joined #css 22:46:37 dbaron has joined #css 23:08:41 jdaggett has joined #css 23:30:11 jet has joined #css 23:38:24 jdaggett_ has joined #css 23:54:34 jdaggett_ has joined #css 23:54:48 dauwhe has joined #css