W3C home > Mailing lists > Public > www-style@w3.org > January 2015

Re: [css-logical-props] resolving against parent's writing mode properties

From: Cameron McCormack <cam@mcc.id.au>
Date: Sat, 31 Jan 2015 10:15:11 +1100
To: fantasai <fantasai.lists@inkedblade.net>
Cc: www-style@w3.org
Message-ID: <20150130231511.GJ3161@wok.mcc.id.au>
fantasai:
> Ideally, I think you'd want to compute margins and borders against the
> containing block, since an English article and a Japanese article in
> the exact same location in a layout should have the same margins and
> borders; whether you have top/bottom borders or right/left borders
> (if you picked only a pair) would usually depend on the context, not
> the contents. Certainly the abspos offsets would depend on the context,
> not the contents, of the abspos element.

I also was thinking that it would make more sense – at least for the
offset-* properties, if you’re placing an element in a position:absolute
context – for them to be relative to the containing block.

> But I'm not sure what's ideal for padding, and containing block relations
> are maybe not so clear when you're in the middle of cascading, and it's
> probably easier for people to remember to just only check the element's
> own properties. It will mean that many use cases will involve wrapper
> elements, though.

I agree; let’s leave this simpler rule.

> >Also, the spec should define what happens when you use one of these
> >logical properties on the root element.
> 
> The root element propagates direction/writing-mode to the initial
> containing block.

[Moot now, but:]  So this means that the root element would end up using
the initial containing block’s writing mode property values to its
logical properties (i.e., it would use the same writing mode values that
are on the root element itself).

-- 
Cameron McCormack ≝ http://mcc.id.au/
Received on Friday, 30 January 2015 23:15:39 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 22:51:57 UTC