Ah, that would explain why clicking on the image made it change. :-)
Actually pretty logical (hate to say it ;-)). However, firefox changes it immediately... so nice that everybody has their own interpretation. :-(
Regards, Sebastiaan Johan Compagner wrote:
IE also triggers onchange, just loose the focus as long as you have the focus on it it doesnt fire. johan On 9/11/07, Sebastiaan van Erk <[EMAIL PROTECTED]> wrote:Hi Eelco, Keyboard actions on components can actually trigger an onClick on the component. I had javascript rendering problems in IE with a checkbox with an onChange that changed an img src. The src of the image would be changed, but IE just refused to update the screen. When I changed the onChange to onClick, suddenly IE did work. However, the point is, that you would expect onChange to fire when you change the value of the checkbox with the keyboard, whereas you would expect onClick not to. However in ALL browsers I tested, changing the value of the checkbox with the keyboard ALSO triggered onClick. Regards, Sebastiaan Eelco Hillenius wrote:Hi, Can anyone please tell me what this: buffer.append("\" onclick=\" var b=Wicket.$('"); buffer.append(submittingComponent.getMarkupId()); buffer.append("'); if (typeof(b.onclick) != 'undefined'){ var r =b.onclick.bind(b)(); if (r != false) b.click(); } else { b.click(); }; return false;\" "); is supposed to do? The idea of adding that hidden submit button there is that it *typically* (depending on the browser and whether multiple forms are nested) would be picked up as the first button by the browser and thus act like a 'default' button that is executed when enter is pushed. I don't really see how it can be clicked on. And is "b.onclick.bind(b)()" a typo? Eelco
smime.p7s
Description: S/MIME Cryptographic Signature
