- From: <bugzilla@jessica.w3.org>
- Date: Mon, 08 Nov 2010 10:58:19 +0000
- To: public-i18n-bidi@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10821 --- Comment #32 from Aharon Lanin <aharon.lists.lanin@gmail.com> 2010-11-08 10:58:17 UTC --- (In reply to comment #30) > (In reply to comment #29) > I think the idea of using "input" is so that generic form validation code or > autocomplete code will re-run if the direction changed. It seems more likely > and more effective to check for form control contents changing using the > "input" event as opposed to mutation events. So if an event is going to be > reused, "input" probably makes more sense. On the other hand, a new event may > be ok as well, since many Web apps will not look at the dir attribute anyway. This justification for using the "input" sounds good to me, although of course I would be ok with a new event too. I would hate to have to rely on a mutation event. DOM2 mutation events have not been interoperably implemented, and are currently deprecated in DOM3. Specifically, DOMAttrModified has not been implemented in WebKit and it is generally unclear whether DomAttrModified is supposed to be triggered on attribute changes done via the browser UI, not via script. As for DOMSubtreeModified, while it is implemented in WebKit, it only seems to be triggered by the initial addition of the dir attribute, but not when its value changes. Furthermore, it has not been implemented in Opera. -- Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug. You reported the bug.
Received on Monday, 8 November 2010 10:58:21 UTC