Hi Everyone -- This code works fine when outside of an UpdatePanel, but when inside, the server side event never gets called.  It works fine in IE (both inside and outside of an UpdatePanel).

Any Ideas?  Code to repro below:

hello.

yes, firefox handles things differently than IE.

the problem occurs on the method _onFormElementClick. you see, when you call the click method programatically, you'll get different results in IE and firefox. to IE, the window.event.srcElement points to the button; however, in firefox, it points to the javascript code you've added to the href attribute.

to be honest, i don't have a clue on which type of behavior is correct. what i'd suggest is opening a bug entry by adding a new post on this forum with the word [BUG] on the title.

Hi there, I am experiencing the exact same error with my application, did you come up with any workaround for this problem?

For me I want to be able to Trigger the update for a specific update panel, but firefox updates them all if the click event is triggered in javascript...

I would be very interested if you had any suggestions...

Thanks,
Dan

<div style="display:none;">
    <asp:Button id="btnHidden" runat="server"
                OnClick="btnHidden_Click"
                UseSubmitBehavior="false"
                />
</div>

I think that what happens in Firefox is that when you call click() on the button it simply invokes all the event handlers and doesn't really do a click operation. And I'm also pretty sure that according to W3C that IE has the correct behavior by truly simulating a click operation. We don't have any plans to make this oddity work with Atlas since there appear to be workarounds. Also I'm not really sure why you'd want to explicitly click a button - it would seem to me that that is just to workaround issues in the app.

Thanks,

Eilon

Garbin, thanks for the solution. Cheer

e.g. its a work around for fire a button when hitting enter in a textbox (searchBox...)

thx a lot! 

This is because IE automatically holds the event object at the window level, whereas Mozilla does not as far as I'm aware.

Whereas in IE you can fire an event, and in the receiving function, identify the caller using event.srcElement, Mozilla requires you to pass the event object as part of the argument in order to identify the caller.  This simply means that instead of using runFunction(), you use runFunction(event).

You can then pick up the caller in Mozilla using event.target.

My experience would lead me to suggest that the window.event property in IE is one of those "Microsoft-only" implementations, and not adherent to any W3C standard; whilst this isn't always a bad thing, Microsoft shouldn't be using it in what is supposed to be a truly "cross browser" capable set of extensions.

Just my two-pennies' worth - I'd be grateful if anyone knows if Mozilla plan to change their model in the future, as to be fair it is a pain to have to pass around the event object.

Hi,

 It's work very good, Thank you very much!!!

 

hello guys I dont know if anybody still needs help but i found this to work:

e.initEvent("click", true, true);

else

lineika, thank you so much for your post. That solved my problem for my firefox issue. I was trying to look for some sort of onclick() event because click() wasn't working in firefox.

You are very very welcome! Glad I could help!