W3C home > Mailing lists > Public > www-style@w3.org > May 2010

Re: [CSSWG] Minutes and Resolutions 2010-04-21

From: Tab Atkins Jr. <jackalmage@gmail.com>
Date: Sun, 9 May 2010 18:56:29 -0700
Message-ID: <v2vdd0fbad1005091856y1ae71f85zd03227fa888f4d87@mail.gmail.com>
To: Boris Zbarsky <bzbarsky@mit.edu>
Cc: "www-style@w3.org" <www-style@w3.org>
On Sun, May 9, 2010 at 6:10 PM, Boris Zbarsky <bzbarsky@mit.edu> wrote:
> On 5/9/10 12:59 PM, Tab Atkins Jr. wrote:
>> Ah, no, I was certainly going to define the auto-offset behavior.
>> Luckily we have much less interop on that, so it's not so much a big
>> deal to redefine.  I was planning on it being the first of the
>> following that exists:
>> * the top-left corner of the border box of the following table-cell
>> * 1px to the right of the top-right corner of the border box of the
>> preceding table-cell
> I'm not sure this does the "right thing" (or at least something that would
> make sense for auto offsets) for rowspanning cells, depending on how you're
> defining "preceding" and "following" (those do need to be defined).

Ooh, good point.

> The "1px to the right" thing doesn't make sense.  You'll end up with gaps
> that way, no?  Unless you don't mean CSS px?  Or unless you're defining
> "corner" in some way that doesn't quite jump out at me, or both.

Sorry, that's meant to specify things to that it won't overlap the
previous cell.  The way I was defining "corner" in my head was
referring to the top-right pixel of the previous cell, and so the next
cell will start 1px over.

Received on Monday, 10 May 2010 01:57:24 UTC

This archive was generated by hypermail 2.3.1 : Monday, 2 May 2016 14:38:34 UTC