Re: [css3-writing-modes] Request to publish Last Call Working Draft

Are the *-start and *-end properties, as implemented in Firefox and WebKit,
relative to the element's direction or the element's parent's direction?
Please note that the same arguments that fantasai brought up for the
"CSS2.1/CSS3WM [issue] on nested bidi and breaking inlines across lines" (
http://lists.w3.org/Archives/Public/www-style/2011May/0186.html) applies to
these properties, in favor of using the element's parent's direction.

Also, do Firefox and Webkit handle the conflict between these values and
*-left and *-right in the same manner? I.e., do they both keep them as
separate properties until they have to be actually used for some element,
and then have the same policy re whether it is the logical or the physical
property that wins?

Aharon

On Mon, May 23, 2011 at 12:29 PM, Alan Gresley <alan@css-class.com> wrote:

> On 21/05/2011 8:16 AM, fantasai wrote:
>
>> All right, I'm all out of open issues, aside from the CSS2.1/CSS3WM one
>> on nested bidi and breaking inlines across lines [1], which needs to be
>> discussed by the WG.
>>
>> So I'm requesting to publish a Last Call Working Draft of CSS3 Writing
>> Modes
>> to trigger a wider review by the i18n community.
>>
>> Here is the latest editor's draft:
>> http://dev.w3.org/csswg/css3-writing-modes/
>>
>> If there are outstanding issues other than [1] that I have not addressed,
>> please bring them to my attention.
>>
>> [1] http://lists.w3.org/Archives/Public/www-style/2011May/0186.html
>>
>> Thanks,
>> ~fantasai
>>
>
>
> Why does the draft spec avoid start and end values. I know that 'beas'
> didn't quite work but I do believe in is safe to use start and end values
> for margin, border, padding and text-align on both inline-level and
> block-level elements.
>
>
> http://css-class.com/test/css/bidi/start-and-end-values.htm
>
>
>
> --
> Alan Gresley
> http://css-3d.org/
> http://css-class.com/
>
>