15:36:13 RRSAgent has joined #css 15:36:13 logging to http://www.w3.org/2009/04/08-css-irc 15:36:21 Zakim, this will be Style 15:36:21 ok, glazou; I see Style_CSS FP()12:00PM scheduled to start in 24 minutes 15:45:00 MikeSmith has joined #css 15:48:42 hi MikeSmith 15:49:07 Lachy has joined #css 15:49:36 glazou: konban wa 15:55:23 Style_CSS FP()12:00PM has now started 15:55:30 +dsinger 15:55:51 dsinger_ has joined #css 15:56:12 Zakim, mute me 15:56:12 sorry, dsinger_, I do not know which phone connection belongs to you 15:56:25 dsinger_: type /nick dsinger 15:56:34 Zakim, who is on the phone? 15:56:34 On the phone I see dsinger 15:56:50 Zakim, mute dsinger 15:56:50 sorry, dsinger_, muting is not permitted when only one person is present 15:57:01 dsinger_: type /nick dsinger into your IRC client 15:57:09 dsinger_: then Zakim will recognize you 15:57:15 Zakim, i am dsinger 15:57:15 ok, dsinger_, I now associate you with dsinger 15:57:17 +glazou 15:57:37 Zakim, mute me 15:57:37 dsinger should now be muted 15:57:59 MikeSmith has left #css 15:58:41 dbaron has joined #css 15:59:14 Zakim, who is on the phone? 15:59:14 On the phone I see dsinger (muted), glazou 15:59:21 +[Mozilla] 15:59:39 Zakim, [Mozilla] has David_Baron 15:59:39 +David_Baron; got it 15:59:42 sylvaing has joined #css 16:00:18 melinda has joined #CSS 16:00:30 +[Microsoft] 16:00:56 Zakim, [Microsoft] has sylvaing 16:00:56 +sylvaing; got it 16:01:04 Can we discuss the sophia agenda briefly? 16:01:10 ChrisL has joined #css 16:01:26 T u 16:01:31 np 16:01:34 +plinss 16:01:48 I only forgot to add it on the agenda but that was on the list 16:02:05 +ChrisL 16:02:15 +Melinda_Grant 16:02:24 +??P13 16:02:29 emilyw has joined #css 16:02:31 Zakim, ??P13 is me 16:02:32 +fantasai; got it 16:03:10 ok emilyw 16:05:14 Chris asks why agenda is member only but minutes are public 16:06:09 Admin is member only, tech is public 16:06:25 scribenick: chrisl 16:06:29 scribe: chris 16:06:33 chair: daniel 16:06:34 +Bert 16:06:56 +Howcome 16:07:12 topic: agenda - member or public 16:07:31 dg: chris suggests sending agenda to the public list 16:07:37 bb: why? no advantage 16:08:21 dd: agenda almost always public. any member -specific stuff is rare and can be discussed separately 16:08:43 I think the current arr. Is odd but right 16:08:48 pl: can post the agenda minus the dial in numbers to the public list 16:09:01 db: publ;ic may have useful feedback 16:09:10 dg: no, not dial in numbers, just topics 16:09:13 mg: if agenda is early enough 16:09:52 bb: don't want to do this, writing for the public takes to much time. unecessary 16:10:01 dg: specific example? 16:10:10 bb: want to hide spelling mistakes 16:10:19 s/dg/sg 16:10:28 Lachy_ has joined #css 16:11:07 pl: how about we send the agenda to the members mailing list and send a synopsis to the public mailing list 16:11:16 Has any public asked? 16:11:19 pl: how about a synopsis of agenda sent to public, plus fuller agenda to member list 16:11:37 cl: dave - no 16:12:04 They see the minutes 16:12:21 db: how would they ask for it without knowing it exists 16:12:45 dg: minor issue, no consensus to move to public agenda. 16:12:56 It is work to fix, and dpes not seem worth it 16:13:02 ... could take more time to sort through public feedback before meeting 16:13:17 cl: ok, thanks for considering it 16:13:29 dg: we stay as we are for the time being 16:13:29 http://lists.w3.org/Archives/Member/w3c-css-wg/2009JanMar/0212.html 16:13:29 topic: CSS2.1 Issue followup 16:13:32 szilles has joined #css 16:13:43 http://wiki.csswg.org/spec/css2.1#issue-24 16:13:43 Everyone had an action to read Bert's email and prepare for discussion 16:13:53 ee: made comments in email 16:13:58 the " apple][ {color: red}" is actually a lot more complicated than Bert said 16:14:00 no, actually, last week's minutes 16:14:17 fantasai: shouldn't this have been sent to the public mailing list? 16:14:17 ee: wasn't berts comment supposed to be sent to public list? 16:14:41 arronei has joined #CSS 16:14:43 db: contents of email seem reasonable but i don't see a proposal 16:14:54 ... two examples look a bit complex 16:14:56 howcome has joined #css 16:15:19 complex in that they're more complicated than stated because of ()/[]/{}-matching 16:15:25 bb: my preference is to not do anything 16:15:32 ... this is as far as I got 16:16:23 +1 for Judy's summary 16:16:32 ee: it doesn't adress selectors. want it to cover selectors and declaration blocks 16:16:44 szilles: ? 16:17:02 ... idea that you match brackets and quotes is clear enough without specific microparsong rules 16:17:06 s/selectors/at-rules/ 16:17:08 s/+1 for Judy's summary// 16:17:41 ee: there is an error in the spec as we changed the wording and introduced a new issue 16:18:12 ... proposal was that the part on malformed declarations was changed to stateents 16:18:21 http://www.w3.org/TR/CSS21/syndata.html#parsing-errors 16:18:28 There's a rule about malformed declarations 16:18:28 ... should be "statements and declarations" 16:18:32 yea 16:19:04 bb: not sure you always know if you are in a statement or not 16:19:13 ee: in one if you are not in a declaration 16:19:26 ..@rule is always a statement 16:19:38 Zakim, who is on the phone? 16:19:38 On the phone I see dsinger (muted), glazou, [Mozilla], [Microsoft], plinss, ChrisL, Melinda_Grant, fantasai, Bert, Howcome 16:19:40 [Microsoft] has sylvaing 16:19:40 [Mozilla] has David_Baron 16:19:46 +[Apple] 16:19:52 -dsinger 16:19:56 zakim, [apple] has dsinger 16:19:56 +dsinger; got it 16:19:58 ee: if you are in a decl skip to end of decl, else skip to end of that statement 16:20:09 bb: no statements inside an @edia 16:20:17 s/edia/media/ 16:20:34 bb: they look like statements, but they aren't according to the grammar 16:21:04 bb: hence the complex email, there are different types of @rules. @media and @page are different 16:21:30 bb: take last example in my email 16:21:55 ... you are at the top level then you see an invalid string. have not started the first statement 16:22:10 ... have to assume you are unless you are clearly not eg a comment 16:22:46 bb: would like it to be as simple as elika says but doubt it is that simple 16:23:03 ee: only unclear case is inside @page in css3 16:23:28 ... so suggest dulplicating the malfored rule for stateents, then add more detail in css3 paged media 16:23:43 s/dulp/dupl/ 16:23:55 dg: good compromise. is it acceptable? 16:24:15 bb: imples an error inside an @rule causes whole @rule to be ignored? 16:24:22 ee: depends on where it occurs 16:24:30 I think in the long run we should have a single grammar that has "unexpected content" productions that match pretty much anything and which correspond to the pieces that get ignored 16:24:37 ... not if the @rulke has declarations. 16:24:58 ... trap points are stzatements and declarations 16:25:06 dbaron: yes 16:25:31 dg: what are the chars that are matched? 16:25:36 s/sg/sg 16:25:37 { ( " 16:25:40 s/dg/sg 16:25:47 ee: brackets and quotes 16:25:50 ChrisL: that's sylvain galineau 16:25:55 yeah so content:"}" does not cause havoc 16:25:56 also [ 16:26:01 and ' 16:26:03 :) 16:26:12 ()/{}/[]/""/'' 16:26:23 dg: any objections to elika's proposal 16:26:36 (none heard) 16:26:43 bb: ok lets try it 16:27:08 RESOLVED: duplicate malformed declarations rule for malformed statements (statements rule to come after declarations rule in the spec) 16:27:19 resolution: duplicate section on malformed declarations for malformed stateents 16:27:30 db: I think in the long run we should have a single grammar that has "unexpected content" productions that match pretty much anything and which correspond to the pieces that get ignored 16:27:49 ... make the production that covers all things that get ignored 16:27:57 .... this is a rather big project 16:28:26 dg: I agree in principle, on desirability and timeline 16:28:27 http://lists.w3.org/Archives/Public/www-style/2009Feb/0299.html 16:28:46 Topic: Issues with CSS2.1 Grammar 16:29:08 http://lists.w3.org/Archives/Public/www-style/2009Feb/0538.html 16:29:24 dg: should a class be a name instead of an ident? 16:29:29 db: why? 16:29:43 ee: think he missed the point odf the section 16:29:52 dg: and why to escape the first digit 16:30:15 ee: comparing css1 and css2, think he is confused. can no longer do this 16:30:21 dg: agree, not an issue 16:30:27 resolved: non-issue 16:30:27 somebody should respond :-) 16:30:53 http://lists.w3.org/Archives/Public/www-style/2009Feb/0538.html 16:31:00 action: daniel to respond to yves saying why ident is not an issue 16:31:00 Created ACTION-138 - Respond to yves saying why ident is not an issue [on Daniel Glazman - due 2009-04-15]. 16:31:13 http://lists.w3.org/Archives/Public/www-style/2009Feb/0538.html 16:31:40 bb: yes, the S token is ambiguous 16:32:15 bb: ok to change the grammar 16:32:34 dg: so remove s* from end of import? 16:32:36 bb: yes 16:33:10 bert's response http://lists.w3.org/Archives/Public/www-style/2009Feb/0619.html 16:33:17 http://lists.w3.org/Archives/Public/www-style/2009Feb/0619.html 16:33:55 pl: agree 16:34:34 bb: yves says its easier if no non terminals can produce an empty string 16:34:40 ... can accept that 16:34:47 dg: any objection? 16:34:51 (non heard) 16:35:01 dg: choices in berts email seem harmless 16:35:11 ... and obvious 16:35:26 resolved: accept berts proposal on gramar 16:35:42 action: bert make the changes in http://lists.w3.org/Archives/Public/www-style/2009Feb/0619.html 16:35:42 Created ACTION-139 - Make the changes in http://lists.w3.org/Archives/Public/www-style/2009Feb/0619.html [on Bert Bos - due 2009-04-15]. 16:36:15 sg: do we have any outstanding 2.1 issues before publication? 16:36:30 dg: no, so lets publish and update as soon as possible 16:37:01 ee: bert and I will check all the edits have been made 16:37:10 db: so i put an issue on the end of the list 16:37:25 +SteveZ 16:37:34 ... font-weight bolder and lighter, want to backport from css3 to css 2.1 16:37:39 issue 111 16:37:39 dsinger has left #css 16:37:51 dsinger has joined #css 16:37:57 cl: is it simple to specify? 16:38:08 db: yes but no proposed text yet 16:38:18 bb: prefer to see actual text 16:38:23 (several) yes 16:38:35 db: fine to publish but there is more stuff to do 16:38:51 ee: boris has some pendingf issues on anonymous tales still to come 16:39:03 resolved: publish and update to css 2.1 asap 16:39:14 Bert, we should schedule a day to coordinate on 2.1 16:39:16 topic: Fallback color on background-image 16:39:28 http://lists.w3.org/Archives/Public/www-style/2009Feb/0536.html 16:39:53 ee: at f2f we decided I would propose text so we don't need to discuss this now 16:39:59 http://lists.w3.org/Archives/Public/www-style/2009Mar/0389.html 16:40:03 topic: Fallback on border-image 16:40:03 http://www.bradclicks.com/cssplay/border-image/Thinking_Outside_The_Box.html 16:40:46 dg: wh can summarise this? 16:41:10 ee: several open issues from discussions with dave hyatt, brad kempers proposal adresses all of them 16:41:18 ... look at his pictures 16:41:54 ... if image fails to load, layout jumps around. also layout changes depending on border-image support 16:42:09 ... so want it to not affect border-width 16:42:16 ... example with a jutting corner 16:42:28 ... make sa lot of sense 16:43:02 ... also says designers want an image where layout aligns with a given point of the image, wants to allow some overflow 16:43:24 ... minor issues to discuss on mailing list, precise syntax, but we should adopt this 16:43:31 hyatt anr roc in gfavour 16:43:36 s/gf/f/ 16:43:45 s/anr/and/ 16:44:09 dg: demoed boder image, people were scared by the nuber of arguments and this adds four more. its hard to remember 16:44:30 ee: maybe a shorthand with individual properties like border-image-offset 16:44:49 .. more understandable at expense of adding more properties 16:45:08 dg: public wants it to be simpler and easier to understand. need to look at very carefully 16:45:19 ... seems to meet web designer's wishes 16:45:36 bb: what if the corerr image is wider than the box itself? 16:45:46 ee: probably it gets clipped 16:46:03 db: there is some rule to explain how to handle this 16:46:11 ee: needs to be worked out in detsail 16:46:31 dg: any objection to moving forward on this proposal 16:46:40 hl: not studied in detail yet 16:47:07 dg: so, do we adopt this direction and develop it further? 16:47:18 ... main issue is relayout which is a big issue 16:47:27 ee: hyatt raised this also 16:47:33 dg: does make sense 16:47:43 dg: any disagreement? 16:47:54 (none heard) 16:48:11 dg: several options, functional notation or shorthand 16:48:25 sg: I like the proposal, but usability of the syntax is a concern 16:49:23 resolved: adopt this direction to avoid relayout but make the syntax easier to understand 16:51:35 rrsagent, make logs public 16:51:52 topic: next f2f in sophia 16:51:54 http://wiki.csswg.org/planning/sophia-2009 16:52:06 dg: need agenda items to help people with travel planning 16:52:14 ee: pleae add topics to the wiki 16:53:05 ds: no specific ones to suggest but might be difficult getting apple dev there as right before out dev conference 16:53:07 Currently known topics: test suites, and grid/matric/template layouts 16:53:19 sz: last day of japan f2f should have a list of topics 16:53:23 ee: will add them 16:54:00 ds: three day meeting all day? 16:54:03 dg: yes 16:54:22 dg: any other items? 16:54:47 hl: think ing on colun break vs page break. any strong opinions? 16:54:58 ee: melinda and i discussing, no opinions yet 16:55:39 hl: want to bring back the column-break-{before, after, inside} rather than having this in the page properties 16:55:56 sz: then you have an interaction problem 16:56:05 hl: yes, needs to be defined 16:56:10 I'm kinda leaning the same way... maybe with a shorthand to combine them...??? 16:56:16 s/colun/column/ 16:56:59 hl: yes, shorthand could be good. will propose text 16:57:06 zakim, list attendees 16:57:06 As of this point the attendees have been dsinger, glazou, David_Baron, sylvaing, plinss, ChrisL, Melinda_Grant, fantasai, Bert, Howcome, SteveZ 16:57:11 adjourned 16:57:13 -[Apple] 16:57:14 -[Mozilla] 16:57:14 -SteveZ 16:57:16 -[Microsoft] 16:57:16 -ChrisL 16:57:17 -Howcome 16:57:20 rrsagent, make minutes 16:57:20 I have made the request to generate http://www.w3.org/2009/04/08-css-minutes.html ChrisL 16:57:33 -Bert 16:57:42 -glazou 16:58:01 Fantasai, for the CSS 2.1 issues, any day is fine starting next Tuesday. 16:58:07 -fantasai 16:58:09 -plinss 16:58:21 meeting: css wg telcon 16:58:40 -Melinda_Grant 16:58:41 Style_CSS FP()12:00PM has ended 16:58:43 Attendees were dsinger, glazou, David_Baron, sylvaing, plinss, ChrisL, Melinda_Grant, fantasai, Bert, Howcome, SteveZ 16:59:07 agenda: http://lists.w3.org/Archives/Member/w3c-css-wg/2009AprJun/0020.html 16:59:11 rrsagent, make minutes 16:59:11 I have made the request to generate http://www.w3.org/2009/04/08-css-minutes.html ChrisL 17:03:28 Bert: ok 17:03:34 Bert: My schedules' pretty flexible 17:03:50 Bert: how about I'll go through the issues list this week and update it to match the minutes 17:04:09 Bert: and then next Tuesday you can go through and make sure all the edits are in 17:04:19 OK 17:04:21 Bert: I'll review them on Tuesday 17:04:30 Bert: since my timezone is later :) 17:04:42 Bert: and if there's any remaining issues you can fix them Wednesday before the telecon 17:04:48 Bert: so we can get a resolution to publish 17:05:11 Bert: sounds good? 18:57:24 Zakim has left #css 19:00:16 plinss has joined #css 20:10:15 arronei has joined #CSS 20:13:08 Arron has joined #CSS 20:16:17 arronei has joined #CSS 20:56:15 arronei has joined #CSS 21:02:25 Arron has joined #CSS 21:06:38 arronei has joined #CSS 21:13:21 arronei has joined #CSS 21:16:28 arronei has joined #CSS 21:27:00 sylvaing has joined #css 21:30:24 arronei has joined #CSS 21:34:24 arronei has joined #CSS 21:37:10 Arron has joined #CSS 21:50:07 arronei has joined #CSS 21:57:54 arronei has joined #CSS 22:02:36 arronei has joined #CSS 22:11:35 Arron has joined #CSS 22:16:22 arronei has joined #CSS 22:17:28 Lachy has joined #css 22:19:54 Arron has joined #CSS 22:52:11 arronei has joined #CSS 23:00:16 Lachy has joined #css 23:27:14 anne has left #css 23:35:42 MikeSmith has joined #css