Re: [css3-lists] Published as WD!

On Fri, Jul 22, 2011 at 1:58 AM, Øyvind Stenhaug <oyvinds@opera.com> wrote:
> On Thu, 21 Jul 2011 18:00:43 +0200, Tab Atkins Jr. <jackalmage@gmail.com>
> wrote:
>> On Thu, Jul 21, 2011 at 2:22 AM, Aharon (Vladimir) Lanin
>> <aharon@google.com> wrote:
>>>>>
>>>>> 1. For a list-item-position:outside list item, the content of a marker
>>>>> is in a separate paragraph for bidi purposes. Its paragraph direction
>>>>> is taken from the list container's direction.
>>>
>>>> The spec seems to be missing details on how this is supposed to work.
>>>
>>>> The spec didn't have these details, but it does now.
>>>
>>> I had assumed that this was implied by the spec's statement that the
>>> list-item-position:outside list item puts the marker in a "separate
>>> marker box". I am glad it has been spelled out.
>>
>> It's in a separate box that is then absolutely positioned.
>
> I don't see where it says explicitly that this position:marker thing counts
> as a form of absolute positioning. (As an aside, I think it's unfortunate
> that CSS 2.1 uses this term to mean something more than just
> position:absolute.)

Good catch!  I've added a line defining that.


>> I don't
>> know whether that puts it in a separate paragraph for bidi purposes or
>> not.
>
> CSS 2.1 and css3-writing-modes say
>
> "User agents that support bidirectional text must apply the Unicode
> bidirectional algorithm to every sequence of inline[-level] boxes
> uninterrupted by a forced (bidi class B) [paragraph] break or block
> boundary."
>
> ("-level" only occurs in CSS 2.1, "paragraph" only in css3-writing-modes).
>
> But "block boundary" seems to be undefined. I'm not sure if it makes most
> sense to define it in one place, to address it every time a new box type is
> defined, or a little of both...

Hm, okay.  Well, it's irrelevant now, as ::markers are now
unicode-bidi:isolate all the time.

~TJ

Received on Friday, 22 July 2011 21:22:22 UTC