16:43:03 RRSAgent has joined #CSS 16:43:04 logging to http://www.w3.org/2010/02/24-CSS-irc 16:43:12 Zakim, this will be Style 16:43:12 ok, glazou; I see Style_CSS FP()12:00PM scheduled to start in 17 minutes 16:43:18 RRSAgent, make logs public 16:56:33 Style_CSS FP()12:00PM has now started 16:56:40 +glazou_sick 16:57:11 LOL 16:57:18 Zakim, glazou_sick is me 16:57:18 +glazou; got it 16:57:53 oyvind has joined #css 16:59:37 +smfr 16:59:44 dbaron has joined #css 17:00:03 -glazou 17:00:08 +[Mozilla] 17:00:21 -smfr 17:00:28 stupid AT&T 17:00:39 +smfr 17:00:59 +glazou 17:01:17 dethbakin has joined #css 17:01:28 +dethbakin 17:02:28 +[Microsoft] 17:02:37 +Bert 17:02:43 sylvaing has joined #css 17:02:53 +SteveZ 17:03:01 + +200000aaaa 17:04:06 +plinss 17:04:21 we have regrets from dsinger, molly and bradk 17:07:07 Scribenick: szilles 17:07:31 DG: Light agenda, mostly from last week 17:08:09 DG: we should start a discussion of coming F2F, agenda items, schedules, attendance 17:08:39 Agenda: 1. Follow up on Image Position and Image Fit 17:08:58 http://lists.w3.org/Archives/Public/www-style/2010Jan/0476.html 17:09:15 BB: Last weeks discussion did not reach a conclusion on anything 17:10:20 BB: Elika proposes and I agree that the rule for "overflow" should be clip the overflowing parts 17:10:57 SMFR: I can see use cases for scrollbars or the above solution; We could go either way 17:12:25 EE: The author can put scroll bars on the replace element it self; e.g. a document inside an iframe. Thus there is no particular need for scroll bars on the box into which the replace element goes 17:13:09 SMFR: I agree with Elika's analysis; clipping makes most sense 17:13:35 DB: no opinion, still trying to understand it, but willing to live with the clipping proposal 17:14:05 Decision: Clipping is the behavior for overflow 17:14:26 1a. Missing "none" 17:15:28 EE: the answer despends on what the model is for negotiation between the box and the replaced element. I suggested one in a reply 17:16:52 http://lists.w3.org/Archives/Public/www-style/2010Feb/0164.html 17:19:28 EE: The "none' value is asserted as necessary for SVG. I am not sure that this is so. 17:20:41 EE: If CSS decides on the view box size and SVG decides how to fill it then there is no need for a 'none' value because SVG setting will be used anyway 17:21:07 ACTION (all) read Elika's answer above 17:21:07 Sorry, couldn't find user - (all) 17:21:43 1c * Fit to content or padding box? 17:21:57 Decision: content box 17:22:10 1d * Don't inherit 17:23:15 DG: It is suggested to not inherit image-postition and image-fit 17:24:02 EE: the use case for inheritance is "nested elements" but it seems to be more important to honor SVG's preserve aspect ratio 17:24:21 yes 17:24:28 SMFR: I am fine with no inheritance 17:24:31 s/nested/nested object/ 17:24:33 BB: me too 17:25:25 Decision: Do what is best for SVG 17:25:52 ACTION (Elika): Find out what is best for SVG 17:25:52 Sorry, couldn't find user - (Elika) 17:26:38 N. B. if what is best for SVG involves no inheritance, then there will be no inheritance 17:27:18 1d Which module does image-fit go into 17:28:10 EE: could move this property out of the page module into the images module which is being actively edited 17:28:30 BB: Paged Media should be back into CR as soon as possible 17:28:38 Zakim, who is here? 17:28:38 On the phone I see [Mozilla], smfr, glazou, dethbakin, [Microsoft], Bert, SteveZ, fantasai, plinss 17:28:40 [Mozilla] has dbaron 17:28:41 On IRC I see sylvaing, dethbakin, dbaron, oyvind, RRSAgent, Zakim, glazou, smfr, szilles, Lachy, anne, jdaggett_afk, arronei, karl, krijnh, plinss_, plinss, Bert, Hixie, fantasai, 17:28:43 ... trackbot 17:29:13 EE: The catch is that there are a bunch of open issues that will delay getting paged media done 17:30:04 PL: HP is implementing it now and will likely want to push this through, perhaps via me 17:31:09 SZ: Who will make the changes? 17:32:16 EE: The problem with making the changes in Paged Media, is that due to references to the CR version from other orgs we cannot move the draft back to WD 17:33:04 The result of this is that the "editor's draft" that is public cannot be reissued so there is a large discrepency between it and the CR draft. 17:34:26 SZ: it is disconcerting that someone is normatively referencing an out of date document whatever its status 17:35:34 EE: There was some print stuff going on at MIPC and some other org; HP could perhaps provide more detail 17:36:02 Zakim, [Microsoft] has sylvaing 17:36:02 +sylvaing; got it 17:36:25 SZ: can we action HP to tell us what they think the constraints are on the paged media module 17:36:55 ACTION (PL): Get information from HP 17:36:55 Sorry, couldn't find user - (PL) 17:37:10 1e A new 'auto' behavior 17:37:24 BB: I do not like it; I think we can do without it 17:37:40 PL: how do we get the default behaviors without it 17:38:16 EE: We can say that we assign the box and the content "filler" does what ever it thinks is right 17:38:52 EE: using the model above, the content filler is given the size of the area to fill and it makes the decision on how to fill it 17:40:07 SG: Would 'auto' be the default behavior then? 17:40:14 Answer: yes 17:41:00 DB: Because "object" is so hard to implement, perhpas we should not force that on every other kind of element 17:41:31 SG and DB: auto should not be the default just because it is good for "object" 17:42:24 DG: do you agree that a new "auto" value is needed? 17:42:25 I think