Hi That's really weird I have done a sample code (using your evalCode function) for testing but it works fine. Could you try it? If it works, it comes from your code. Why do you use this eval code method? I would be better to have a simple JS function called at onclick event. I did it on PWC documentation because you can edit JS code online, in your case it does not make sense.
Seb <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN" "http://www.w3.org/ TR/xhtml11/DTD/xhtml11.dtd"> <html> <head> <meta http-equiv="Content-Type" content="text/html; charset=utf-8"/> <title>Test</title> <script type="text/javascript" src="../javascripts/prototype.js"> </ script> <script type="text/javascript" src="../javascripts/window.js"> </ script> <script type="text/javascript" src="../javascripts/debug.js"> </script> <script type="text/javascript" src="../javascripts/effects.js"> </ script> <link href="../themes/default.css" rel="stylesheet" type="text/css" > </link> <link href="../themes/alert.css" rel="stylesheet" type="text/css" > </link> <title>Test TextArea</title> <body> <div id="siteFeedback" onClick="evalCode('open_feedback'); return false"> Feedback </div> The snippet with the javascript that opens the window is here: <div style="display:none" id="open_feedback_codediv"> <xmp id="open_feedback"> Dialog.alert("Dialog test", {windowParameters: {width:300, height:100}, okLabel: "close"}); </xmp> </div> <script> function evalCode(id) { var element = $(id); var code = element.innerHTML; code = code.gsub("<", "<"); code = code.gsub(">", ">"); eval(code); } </script> </body> </html> On Feb 4, 2007, at 4:26 AM, Van wrote: > On 2/3/07, Paul <[EMAIL PROTECTED]> wrote: >> I get this. In my case, I reduce the IDs for a particular >> 'reloading' dialog >> that appears from time to time. >> >> I don't think the problem is related to Firebug for me. In my >> case, i have 2 >> buttons that will make the info dialog appear for a few seconds. >> If i click one >> button (dialog appears), and then attempt to click the other >> button as the >> dialog fades out, it'll cause the dialog to be shown again BEFORE >> its finished >> fading away. >> >> I think this could be solved if the background div (that blocks >> all the clicks >> to the page) could be kept until the dialog is completely faded, >> and then >> destroyed all at once. that way, any further clicks to the page >> will occur >> AFTER the window has been removed from the DOM. >> >> right? > > That may work for your situation. In mine, there is no second click > invovled. The first click triggers two instances to be loaded. There > are no happy fingers involved here makeing extra mouse clicks anywhere > on the page. > > -Van > >> >> cheers >> Paul >> >> Van wrote: >>> And click on the feedback link in the upper right corner of the >>> page. >>> An alert gets displayed warning that, "Window feedbackDialogId is >>> already registered in the DOM!" This is happening because our user >>> feedback dialog gets opened twice for a single click on that >>> link. The >>> snippet of the page where the link is defined is this: > > _______________________________________________ > Javawin mailing list > [email protected] > http://mail.xilinus.com/mailman/listinfo/javawin_xilinus.com _______________________________________________ Javawin mailing list [email protected] http://mail.xilinus.com/mailman/listinfo/javawin_xilinus.com
