- From: <bugzilla@jessica.w3.org>
- Date: Thu, 27 Jan 2011 14:39:50 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=11129 --- Comment #18 from Mounir Lamouri <mounir.lamouri@gmail.com> 2011-01-27 14:39:49 UTC --- So, there is still one situation mentioned by Hixie in comment 2 that hasn't been discussed: when form controls are "all over the place". I guess that means: <form id='f'></form> <input form='f' name='a'> <input form='f' name='b'> <output form='f' onforminput="value=parseFloat(a.value)+parseFloat(b.value);"> In that case we can't indeed use the capture or bubbling phases of the input and change events but I think there is no reason to care too much about this case given that I guess the real use cases to have form controls not descendants of their form owners is when they are very far away in the tree and I would guess that should not happen when you want to have an interaction between form controls. At worst, it's always possible to do it but it would be more painful: <form id='f'></form> <input form='f' name='a' oninput="updateOutput();"> <input form='f' name='b' oninput="updateOutput();"> <output form='f' name='o'> <script> function updateOutput(aForm) { aForm.o.value = parseFloat(aForm.a.value) + parseFloat(aForm.b.value); } </script> -- Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug.
Received on Thursday, 27 January 2011 14:39:51 UTC