W3C home > Mailing lists > Public > www-style@w3.org > September 2013

Re: [cssom-view] More getBoxQuads/convert*FromNode issues

From: Tab Atkins Jr. <jackalmage@gmail.com>
Date: Fri, 20 Sep 2013 15:26:07 -0700
Message-ID: <CAAWBYDBTVC+Xv62_nGAptYcBBATwjmX=iL2vkkWy37dOCsrrKw@mail.gmail.com>
To: "Robert O'Callahan" <robert@ocallahan.org>
Cc: www-style <www-style@w3.org>
On Fri, Sep 20, 2013 at 3:09 PM, Robert O'Callahan <robert@ocallahan.org> wrote:
> On Sat, Sep 21, 2013 at 5:19 AM, Tab Atkins Jr. <jackalmage@gmail.com>
> wrote:
>>
>> But yeah, your choice seems reasonable here.  Having border-box return
>> something other than the box that the border surrounds would be
>> super-confusing and bad.  Having margin-box return something other
>> than the extent of the margins would be super-confusing and bad.
>> Having the two differ by more than just the size of the margins is
>> also confusing and bad, but less so I think - it makes the feature
>> less consistent between results, but keeps each individual call
>> consistent.
>
>
> OK good.
>
> One thing we could do to help is introduce additional box types
> "margin-inside" and "border-inside" to let authors cope with tables (where
> there is content between the border-box and the inside of the margins) and
> scrolled elements (where there is content between the padding-box and the
> inside of the borders). This could be done as a later extension if we find
> it's needed.

Yeah, makes sense as a later addition.  Should probably be recorded as
a note in whatever spec this is going in.

~TJ
Received on Friday, 20 September 2013 22:26:53 UTC

This archive was generated by hypermail 2.4.0 : Friday, 25 March 2022 10:08:34 UTC