W3C home > Mailing lists > Public > public-i18n-bidi@w3.org > July to September 2010

Re: per-paragraph auto-direction, a.k.a. dir=uba

From: Ehsan Akhgari <ehsan@mozilla.com>
Date: Wed, 25 Aug 2010 09:23:41 -0400
Message-ID: <AANLkTikzrsmcU31bF_tBBb0dQGeLTnFSGBno33my4QdN@mail.gmail.com>
To: "Aharon (Vladimir) Lanin" <aharon@google.com>
Cc: Behdad Esfahbod <behdad@behdad.org>, Adil Allawi <adil@diwan.com>, Shachar Shemesh <shachar@shemesh.biz>, public-i18n-bidi@w3.org
On Wed, Aug 25, 2010 at 8:41 AM, Aharon (Vladimir) Lanin
<aharon@google.com> wrote:
> Whether the default behavior of <textarea> should / can change is a separate
> question. But to achieve this more limited goal without running into the
> problems described above, we could allow dir=uba on just two elements:
> <textarea> and a new element that we could call <textareadiv> or perhaps
> <plaintext>. The latter would be just like a <pre> except that:
> It would not allow mark-up (in the same way that <textarea> does not allow
> mark-up).
> It would have the same script-accessible properties as <textarea>, including
> a settable value property.
> In other words, it would be the output counterpart of <textarea>. In terms
> of CSS, dir=uba would result in unicode-bidi having the new value "uba"
> (which is only allowed on <textarea> and <plaintext>); the element would
> inherit direction as normal, but its effect under unicode-bidi:uba would be
> limited to when the content is completely neutral.

What purposes would the second element serve?  I don't see its
advantage over <textarea>.

Received on Wednesday, 25 August 2010 13:25:27 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:24:37 UTC