- From: <bugzilla@jessica.w3.org>
- Date: Mon, 08 Nov 2010 08:50:11 +0000
- To: public-i18n-bidi@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10821 --- Comment #30 from Maciej Stachowiak <mjs@apple.com> 2010-11-08 08:50:11 UTC --- (In reply to comment #29) > Would mutation events or their replacement not cover this? (If a generic event > such as 'input' is sufficient, mutation events or their replacement should be > too.) 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. -- 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 08:50:13 UTC