- From: fantasai <fantasai.lists@inkedblade.net>
- Date: Wed, 26 Aug 2009 13:03:44 -0700
- To: www-style@w3.org
Summary:
- Tab Atkins added as co-editor of css3-images (to work on gradients proposal)
- RESOLVED: replaced elements clip to the border-radius curve
- Discussed consecutive run-ins.
====== Full minutes below ======
Present:
Tab Atkins (Invited Expert)
Bert Bos
Arron Eicholz
Elika Etemad
Sylvain Galineau
Brad Kemper
Anne van Kesteren (via IRC)
Peter Linss
David Singer
Steve Zilles
<RRSAgent> logging to http://www.w3.org/2009/08/26-CSS-irc
Scribe: Sylvain
<bradk> Hi Tab. Welcome to the group.
<TabAtkins> Yo, bradk
Agenda / Administrative
-----------------------
plinss: Hyatt not here, skipping gradient
plinss: same for box shadow without David Baron or Chris Lilley
RESOLVED: Tab Atkins co-editor of CSS3 Images
Replaced Elements and border-radius
-----------------------------------
<plinss> http://lists.w3.org/Archives/Public/www-style/2009Jun/0115.html
brad: I uploaded a page re: border-radius clipping for replaced elements
<bradk> http://www.bradclicks.com/cssplay/curved-corner-image.html
fantasai: I updated the spec to make replaced elements clipped to the curve
fantasai: It looks wrong if you clip to the padding or border edge when
there's padding
fantasai: there is no use case for replaced element to clip outside their
content box either
brad: I agree with fantasai's proposal
arronei is in agreement for replaced elements
RESOLVED: replaced elements clip to the border-radius curve
display: run-in
---------------
<plinss> http://lists.w3.org/Archives/Public/www-style/2009Aug/0120.html
<plinss> http://lists.w3.org/Archives/Public/www-style/2009Aug/0427.html
issue 128: http://lists.w3.org/Archives/Public/www-style/2009Jul/0025.html
proposal: http://lists.w3.org/Archives/Public/www-style/2009Aug/0427.html
fantasai: We probably want approval from bz and/or dbaron before going
anywhere with this...
fantasai: Tab's point that run-ins should run into each other is good
bert: this is currently defined and runs counter to the current prose...
bert: I am ok to change it but be aware that this is a change
bradk: any downside ?
bert: none aside from being different from what implementations do....
tab: I haven't come up with a case where I wouldn't want this to happen
<Bert> <h2>first</> <!-- no content yet --> <h2>Second</> <p>text...
plinss: if I have the run-in header-paragraph pattern and one of my sections
has no paragraph I may still want the header with no content to not
run into the next section
<Bert> Counter example, where run-in into run-in makes sense:
<dt>Term 1 <dt>Term 2 <dd>Defintion.
bradk: could you do :before {content:"\n";}
bert: yes, if you know what to select
<Bert> h2 + h2:before {content: "\A"} makes the double run-in look a little
less like a run-in....
<Zakim> +SteveZ
<anne> Bert, if you have two definitions that would look weird though, methinks
* anne thinks run-in is a bit weird anyway
* sylvaing is totally unable to scribe this
szilles and tab discuss bert's dt/dd example
tab: an alternative is to use floats which cause a number of other problems
howcome: I don't think the benefit of this is worth breaking interoperability
with existing implementations
tab: the cases we talk about here may be addressed with other solutions
fantasai: another solution is to add another display type
howcome: run-run-in ?
* Bert so often runs into the problem that dt/ddd is missing a wrapping
<di> element. :-(
<TabAtkins> ::di, obviously
<anne> Bert I tried getting it into HTML5 but so far without luck
<Bert> no, ::di doesn't work, because I want to distinguish
<di><dt>term w/o defn</di> from <di<dt>term1<dt>term 2<dd>defn</di>
<TabAtkins> empty <dd>?
* TabAtkins supposes that might not be right.
<anne> Bert, not having a <dd> is non-conforming
<plinss> adjourned, didn't get critical mass to address most of the agenda topics
<anne> if people could quickly review the MQ changes that'd be cool
<anne> Bert, is anything else needed for republication of a CR when there's
WG approval?
<anne> Bert, can we maybe publish CSS 2.1 again as well so it has the
media_list production?
<Bert> Nothing special is needed, just a corrected document and a date from
the webmaster.
<Bert> If we want to re-publish CSS 2.1, we can do that , too.
<Bert> (as long as we make only editorial changes, but that is indeed the
case here.)
<anne> i guess we have to wait another week to decide on publishing CSS 2.1?
<Bert> Yes,we need a recorded WG decision.
<anne> ok, lets wait for that then
<anne> that gives people some time to study my email too, if anyone does
Received on Wednesday, 26 August 2009 20:04:29 UTC