See also: IRC log
<glazou> This will be my 4th conf call in a row, please excuse if some of my neurones fused...
<glazou> regrets from molly and jeffrey
<dbaron> yeah, the tapping noise was glazou
<arronei> I'm only on IRC today.
<glazou> hi arronei, np
<fantasai_> ScribeNick: fantasai_
<arronei> Hi, its my birthday today so I am trying to take it easy.
Happy Birthday :)
<glazou> happy birthday arronei!!!!!
<Bert> Congratulations!
<glazou> what are doing here then ?
<glazou> you
<arronei> I still love CSS.
<glazou> ROTFL
<Bert> :-)
<sylvaing> ...against all odds...
<jason_cranfordtea> well why don't you marry it then
<Bert> lol
<glazou> lol
<arronei> no marriage is a bit too far for me right now
Daniel: Any other items for
agenda?
... I tried to get agenda items from both mailing lists, let me
know if I missed any
Daniel: Charter was sent by IJ to
list of AC reps for approval and vote
... In case they missed it, I suggest you ping your AC reps to
let them know that the charter is up for approval
... In the voter form, the AC rep needs to indicate intent or
not to join WG
... It's important, please don't miss it
<glazou> http://lists.w3.org/Archives/Member/w3c-css-wg/2008JulSep/0248.html
Daniel: First issue is about potential change in 'direction' of marquee
<glazou> Note that the 'direction' property is often set by rules
<glazou> in the UA style sheet based on mark-up in the document, as
<glazou> recommended in CSS 2.1 [CSS21] section 9.10 ("Text direction:
<glazou> the 'direction' and 'unicode-bidi' properties").
fantasai: works for me, I think we should add it
RESOLUTION: Accepted to add Bert's note
Daniel: Question is shall we
publish css3-marquee as CR.
... Got 2 comments from i18n, above and one other, both are
resolved.
... Any objections to moving to CR?
RESOLUTION: Publish CSS3 Marquee as CR
<scribe> ACTION: Bert publish CSS3 Marquee as CR [recorded in http://www.w3.org/2008/10/01-css-minutes.html#action01]
<trackbot> Created ACTION-109 - Publish CSS3 Marquee as CR [on Bert Bos - due 2008-10-08].
<scribe> ScribeNick: fantasai
Daniel: Many recent comments
about spec, mostly from Saloni
... First one
<glazou> http://lists.w3.org/Archives/Public/www-style/2008Sep/0198.html
http://lists.w3.org/Archives/Public/www-style/2008Sep/0198.html
<Bert> (Publishing moratorium is 13 Oct - 27 Oct)
Peter: The more I think about it,
the more I think we should not allow comments in URLs
... comment delimiters are valid URL syntax, and URLs have a
special tokenization
... you're not in normal CSS rules
... There are places where you can determine whether it's a
comment or part of URL
... other places where you can't
dbaron: Are there any browsers that don't do what you think we should do?
Peter: I talked with
zweinberg
... Opera does not allow comments within parentheses
dbaron: I'm ok with the proposal given that
Jason: I did a quick search, don't see anyone using it as a hack either
<dbaron> I agree with Peter about how it should work.
Peter: IE7 and Gecko allow comments
Daniel: So if proposal is
accepted, there's no change for Opera, slight change for
Mozilla and IE
... David is ok with it
... What about MS?
dsinger: Anyone know about webkit?
<Bert> Konqueror seems not to allow comments.
<scribe> ACTION: Saloni return to WG with response about whether proposal is accepted [recorded in http://www.w3.org/2008/10/01-css-minutes.html#action02]
<trackbot> Created ACTION-110 - Return to WG with response about whether proposal is accepted [on Saloni Mira Rai - due 2008-10-08].
<Bert> Webkit seems the same as Konqueror.
dbaron: So my understanding is no change to the spec
Daniel: We might need a note saying that it's explicitly forbidden
Peter: There are various bits of
text in the spec that talk about comments
... Saying that they're allowed between any tokens
... and URL is one token
<scribe> ACTION: Peter create note about how URL has its own syntax and parsing rules [recorded in http://www.w3.org/2008/10/01-css-minutes.html#action03]
<trackbot> Created ACTION-111 - Create note about how URL has its own syntax and parsing rules [on Peter Linss - due 2008-10-08].
Peter: I also noticed that the grammar for URL leaves out a-z and 0-9
dbaron: There might be a range in there that doesn't look like a range
Peter: I didn't see one
dbaron: *-~ is a range, and includes everything you mentioned
<glazou> http://lists.w3.org/Archives/Public/www-style/2008Sep/0228.html
fantasai: I am strongly in agreement with the proposal
http://wiki.csswg.org/spec/css2.1#issue-74
RESOLUTION: Accepted
<glazou> http://lists.w3.org/Archives/Public/www-style/2008Sep/0152.html
Saloni: With fixed table layout
in CSS, if a row has more columns than the first row
... The spec says you shouldn't render those columns, but the
browsers actually do render those cells
... I understand the value of fixed layout, I think it's
important
<glazou> np Moz
Saloni: So I propose relaxing the requirement in CSS2.1, and then clarify in CSS3 what exactly should happen
<glazou> regrets now: molly, jeffrey, mohamed
dbaron: That would leave internal contradictions in the spec
fantasai: we could say that if
there are extra cells, rendering is undefined
... or at least the widths of columns and the table are
undefined
<sylvaing> agrees with Elika+Saloni
Saloni: So we'd be saying if you have fixed table layout, and extra cells, the layout is undefined
<scribe> ACTION: Saloni propose text for CSS2.1 Issue 75 [recorded in http://www.w3.org/2008/10/01-css-minutes.html#action04]
<trackbot> Created ACTION-112 - Propose text for CSS2.1 Issue 75 [on Saloni Mira Rai - due 2008-10-08].
<glazou> http://lists.w3.org/Archives/Public/www-style/2008Sep/0153.html
Saloni: That's resolved, we got an explanation of why this rule is in place
<glazou> http://lists.w3.org/Archives/Public/www-style/2008Sep/0229.html
http://wiki.csswg.org/spec/css2.1#issue-76
<dsinger> at&t signal trouble, sorry
<glazou> np dsinger
<dsinger> no, the apple call is not jcraig but dsinger
When formatting content in the page model, some content may end up outside the *current* page box. For example, an element whose 'white-space' property has the value 'pre' may generate a box that is wider than the page box. Also, when boxes are positioned absolutely *or relatively*, they may end up in "inconvenient" locations. For example, images may be placed on the edge of the page box or 100,000 meters below the page box.
Daniel: Change "Also" to "As another example"
RESOLUTION: Accepted above proposal
<glazou> http://lists.w3.org/Archives/Public/www-style/2008Sep/0233.html
Daniel: "Parts of the fixed position box that are not visible in the initial containing block will not print"
RESOLUTION: Proposal accepted with above change.
<glazou> http://lists.w3.org/Archives/Public/www-style/2008Sep/0232.html
http://wiki.csswg.org/spec/css2.1#issue-77
<glazou> plinss, can you take the floor for a minute please ?
<glazou> or Bert ?
Added to agenda for TPAC
http://lists.w3.org/Archives/Public/www-style/2008Sep/0230.html
fantasai: Jason, I think we'll want your feedback on this issue
<Bert> (Prince shows a fourth option: the box is 500px high on *both* pages. I don't particularly like that solution.)
fantasai: So I think the distance
between the bottom of the last content on the page that fit and
the bottom of the page should not count as part of the used
height
... So in this case you would still have used height left over
that you use on the next page
... Whether the background prints in that space is a separate
issue
Jason: I should be able to be online 9-5 EST during TPAC
Daniel: Postponed to TPAC
<glazou> postponed
dbaron: Given that anne isn't here, we should postpone that one
<glazou> plinss: ping
<plinss> ack
<dbaron> Oh, the TPAC is a week further away than I was thinking it was.
<dsinger> jcraig was an illusion
<dsinger> that was me
<glazou> dsinger: tss tss :-)
<dsinger> I don't know how to tell Zakim that that is the apple corporate line (I re-dialed from my desk)
<dbaron> I emailed dsinger with the URL http://www.w3.org/1998/12/bridge/info/name.php3
RRSAgent: make logs public
Bert, let me know when you get around to making all the outstanding CSS2.1 edits
RRSAgent: make minutes
This is scribe.perl Revision: 1.133 of Date: 2008/01/18 18:48:51 Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/ Guessing input format: RRSAgent_Text_Format (score 1.00) Succeeded: s/dbaron:/Peter:/ Succeeded: s/third/fourth/ Found ScribeNick: fantasai_ Found ScribeNick: fantasai Inferring Scribes: fantasai_, fantasai Scribes: fantasai_, fantasai ScribeNicks: fantasai_, fantasai Default Present: plinss, glazou, +1.425.533.aacc, sylvaing, David_Baron, jason_cranfordtea, DaveS, fantasai, Bert, SaloniR, jcraig Present: plinss glazou +1.425.533.aacc sylvaing David_Baron jason_cranfordtea DaveS fantasai Bert SaloniR jcraig WARNING: No meeting title found! You should specify the meeting title like this: <dbooth> Meeting: Weekly Baking Club Meeting Agenda: http://lists.w3.org/Archives/Member/w3c-css-wg/2008OctDec/0000.html WARNING: No meeting chair found! You should specify the meeting chair like this: <dbooth> Chair: dbooth Got date from IRC log name: 01 Oct 2008 Guessing minutes URL: http://www.w3.org/2008/10/01-css-minutes.html People with action items: bert peter return saloni WARNING: Input appears to use implicit continuation lines. You may need the "-implicitContinuations" option.[End of scribe.perl diagnostic output]