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
