#Firefox vs internet explorer 7 code

You'll just have to rethink your strategy. Like I said, dismissing the alert first causes infinite looping, while dismissing the prompt does not.Īt any rate, I think the issue is the event-handling architecture. You need to realize that when you are dismissing the alert/prompt windows, you are implicitly firing the onblur event. > Order of firing isn't the problem eitherįrom what I tested, order of firing does make a difference. Logically, the nesting should be with the elements because they are the ones that contain the references to the event handlers, the the problem is they are not 'container' elements. I believe the nesting would work if the elements were 'container' elements (.) and then nest them, since the events are on the elements rather than the div. I tried to nest them within divs but it did not work either: >changing the order of event handling will not work, as those commands deal with nested elements.Īgree. FF seems to Fire and event and regardless of its outcome, it immediately goes to the next event and executes it. Successively implies one after the other. >If function1 and function2 are fired off in successively But what I found most interesting is the 'infinite' loop that takes place if the alert window is closed before the prompt. Meaning, the form ultimately submits no matter what. If instead I move the alert to the side and then click the cancel on the confirm and then click OK on the alert, Then I see the 'problematic' behaviour you are referring to. On my system, the alert appears on top of the prompt and as soon as I click OK, it goes into some sort of an infinite loop, seemingly triggered by repeatedly setting the onblur event.

#Firefox vs internet explorer 7 code

When I run you code (FF 2.x, WinXP SP2) as soon as I click on the button, I see two 'popups': What I find more interesting is that it seems the results I am seeing are quite different from yours. On another note, I understand what you are trying to do on the code above, but I can't 'fix' it to suit your needs. You may find the following article useful: Your problem seems to be related to the different ways in which browsers implement event handling. Thanks much in advance for any information Test onblur FF vs IE function procApple(typeApple) Apple Through to the onclick unless the prompt gets a positive response? Why does this happen and how can I alter my code to work the same inīoth browser, such that Firefox will do the onblur code and not fall In Firefox the prompt will come up to but processing will fall through However, in IE processing will halt in the first function for onblurĪnd if I press cancel in the resulting prompt, processing will The text field to the button and press the button. In both browsers, both functions will fire when I move the mouse from The top one has a function connected to the onblur event

In the HTML page below I have a text field and a submitīutton. I'm noticing that IE and Firefox handle onblur events slightlyĭifferently.