Issue 107: IE6 refreshes page on nyroModal fire.
Status:  Fixed
Owner: ----
Closed:  Jan 2009
Reported by jason.ka...@gmail.com, Oct 31, 2008
What steps will reproduce the problem?
1. Use nyroModal with type iframe or ajax (filtered/local content)
2. Type information into form fields (unrelated to nyroModal links)
3. Click on nyroModal link
4. Page refreshes losing any information typed into the form
5. modal pops up correctly with proper data

What is the expected output? What do you see instead?
I expected all to work as it does, without refreshing the page (and hence,
losing form data).

What version of the product are you using? On what operating system?
Using 1.3.0 on WinXP SP2/IE6 (works fine with IE7)

Please provide any additional information below.
To reiterate, the page is being run locally and links are pointing to
another local html page. (from page1.html: href="help.html#q123") The form
in question is on page1. Any data that is typed into the form before
clicking a nyroModal link is lost up execution of nyroModal. Yes, I am
doing event.preventDefault() (and I've also tried event.stopPropogation()
and return false;) 
Oct 31, 2008
#1 jason.ka...@gmail.com
Further information: I've continued testing and must elaborate further. I am using a
WebBrowser control in a VB6 app. The webbrowser control uses IE as installed on the
machine. I tried testing the page refresh issue using the real Internet Explorer and
the issue does not re-occur. Thus, I must assume there is some additional events
firing (or not being blocked) specific to the WebBrowser control itself. This still
remains an issue, so if anyone has any suggestions, I am open to them. However, at
this time I do not believe this is actually a bug with nyroModal.
Oct 31, 2008
Project Member #2 nyro...@gmail.com
Could you send a link where I can see the bug please?
Oct 31, 2008
#3 jason.ka...@gmail.com
I've discovered the source of the bug. IE6 seems to be firing a DocumentLoaded event
(A VB WebBrowser control event) on completion of the loading of the Ajax content. Our
own handler for this event was then causing the problem. This bug can be closed.
Jan 27, 2009
Project Member #4 nyro...@gmail.com
(No comment was entered for this change.)
Status: Fixed