W3C home > Mailing lists > Public > www-style@w3.org > August 2012

Re: [cssom-view] value of scrollLeft in RTL situations is completely busted across browsers

From: Glenn Adams <glenn@skynav.com>
Date: Thu, 9 Aug 2012 03:36:01 -0600
Message-ID: <CACQ=j+fKbPKqQPwpQfYfcJqm6HkavWhKpRqM=6Q1d1CwU-q7OQ@mail.gmail.com>
To: Shane Stephens <shans@google.com>
Cc: robert@ocallahan.org, www-style@gtalbot.org, www-style <www-style@w3.org>, ML publc-i18n-bidi <public-i18n-bidi@w3.org>
On Wed, Aug 8, 2012 at 11:33 PM, Shane Stephens <shans@google.com> wrote:

>
>>> Based on this data, I propose we adopt the Gecko/Opera behavior for both
>>> viewport and non-viewport scrolling. (I assume everyone agrees that Webkit
>>> treating them differently is a bug.)
>>>
>>> If we need a property that always starts at 0 and progresses left in RTL
>>> situations, I suggest creating a new "scrollHorizontal" property for that.
>>
>>
>> I agree. scrollLeft should express legacy behavior (to the extent we can
>> agree on a norm), and a new method can be defined to effectively abstract
>> writing mode;
>>
>>
> I'm quite happy with this approach too.
>
> Would we then agree with Rob's original suggestion ("I think most Web
> content I've seen that uses scrollLeft assumes its minimum value is zero
> and it increases from left to right" - the key here is that the minimum
> maps to the left hand edge) as a specification for scrollLeft? Or
> alternatively explicitly denote that scrollLeft is legacy and undefined for
> RTL content?
>

I prefer Rob's original suggestion; i.e., I prefer that left means left.
Received on Thursday, 9 August 2012 09:36:55 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 17:20:58 GMT