On 1/9/07, Jorge Godoy <[EMAIL PROTECTED]> wrote:
> I'll try more, but I'm almost giving up on this generic approach...
I did some searching of my own last night, couldn't come up with
anything that specifically handled onchange in a generic manner. I
also didn't find any articles complaining about it, which was weird.
The call signal(window,'onchange') uses a completely different
codepath, so that's not really a good test of what wrong here.
If you don't figure out a solution, I'd add a class to each
input/select that I'm looking to watch and do:
connect(getElementsByTagAndClassName('input','changes'),'onchange',action())
connect(getElementsByTagAndClassName('select','changes'),'onchange',action())
Instead of sticking onclick= handlers on everything. It's not an ideal
solution and you can special-case IE if you like and handle onchange
at the window level for everything else.
Just another reason webdevs hate IE...
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"MochiKit" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/mochikit?hl=en
-~----------~----~----~----~------~----~------~--~---
