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

Re: events on user setting text direction

From: Ehsan Akhgari <ehsan@mozilla.com>
Date: Mon, 27 Sep 2010 19:38:07 -0400
Message-ID: <AANLkTiksmv9GwC==F-XL8P26+tCeGi38z-XCerj0JD1h@mail.gmail.com>
To: "Aharon (Vladimir) Lanin" <aharon@google.com>
Cc: public-i18n-bidi@w3.org
 On Mon, Sep 27, 2010 at 3:37 PM, Aharon (Vladimir) Lanin <aharon@google.com
> wrote:

> At the face-to-face, we said:
>
> > (Section 3.8)
> >
> > 28. There is no need to trigger the oninput event
> > when the user explicitly sets the direction of an
> > <input> or <textarea> element since the dir
> > attribute change that this causes should generate
> > the DOM2 DOMAttrModified event
>
> It turns out that this is not exactly true. WebKit currently does not
> support DOMAttrModified and it is unclear if they ever will. Firefox,
> apparently, supports it, but only triggers it when an attribute is changed
> by script, not by the browser UI (as would be the case for setting text
> direction). And finally, DOM3 deprecates all the mutation events,
> including DOMAttrModified. They are supposedly working on an alternative,
> but we have no idea whether it will actually come to be or if it will apply
> to our case. Thus, I am leaving the original suggestion to trigger the
> oninput event when the user explicitly sets the direction.
>

Given the concerns you mentioned here (well, all except for the first one!),
I think that's a good choice.  There is one point though, how are web page
scripts supposed to determine whether the input event has been raised
because of direction change or because of actual input?  Should we use a
property on the event object?

--
Ehsan
<http://ehsanakhgari.org/>
Received on Monday, 27 September 2010 23:39:40 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 27 September 2010 23:39:46 GMT