Well, "change" can be problematic in Internet Explorer because the browser doesn't always trigger that event until the control loses focus.
On Fri, Sep 11, 2009 at 12:33 AM, Jules <jwira...@gmail.com> wrote: > > You are right, when click() event is triggered, the check box/radio > button value is the original value. Use change(fn) to detect the > after click() value. > > On Sep 11, 10:40 am, Mike McNally <emmecin...@gmail.com> wrote: >> Am I the only person who finds wildly wrong the jQuery behavior of >> handler invocation for native events on state-changing elements like >> check boxes and radio boxes? Specifically, when the user clicks a >> check box or a radio box, the state of the element is changed and then >> the handler is invoked. However, when I call "click()" on the >> elements, the handler is invoked *before* the element value is >> updated. That makes it pointlessly difficult to write handler routines >> that need to look at the value to know what to do. >> >> Am I just doing something wrong? This is something I've been dealing >> with for years now and it's always driven me nuts. >> >> -- >> Turtle, turtle, on the ground, >> Pink and shiny, turn around. -- Turtle, turtle, on the ground, Pink and shiny, turn around.
