On 2/4/07, Van <[EMAIL PROTECTED]> wrote:
> On 2/3/07, Sébastien Gruhier <[EMAIL PROTECTED]> wrote:
> > 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>
>
> Hmmm. This seems logically equivalent to what I am doing already
> except for the JS function evalCode being within the page directly
> rather than coming from separate included JS file. It looks like I
> will have to simplify my version until I find the aspect of my full
> configuration of page and included JS files that is the problem. :-(
>
> I'll report back when I have either resolved it or found a simpler
> reproducable test case.
Okay. I have narrowed it down to the point you should be able to
reproduce it in a simple test case. It requires that you use a
synchronous AJAX request to load content into a dialog. Here is dialog
call that should fail for anybody with FireBug 1.0 installed on
Firefox 1.5 or 2.0 with PWC version 0.98:
Dialog.alert({url: "http://www.krillion.com/ajax/xA-feedbackSetup";,
options: {method: 'get', asynchronous:false}},
{windowParameters: {width:600, height:350},
id: "dialogTestId"});
This example should work in your test environment too because I fully
qualified the AJAX request to get the content from our public site. Of
course, you could use your own local content for the AJAX component of
this test.
It is definitely an interaction of FireBug 1.0 in the environment and
making an asynchronous AJAX call to load dialog content. When I remove
the synchronous request configuration so that it is done
asynchronously, the problem disappears for this version of the call:
Dialog.alert({url: "http://www.krillion.com/ajax/xA-feedbackSetup";,
options: {method: 'get'}},
{windowParameters: {width:600, height:350},
id: "dialogTestId"});
I hope this helps you to figure out what the problem is with
synchronous AJAX calls. In the mean time, I'll have to figure out if I
can workaround the reason I was loading them synchronously in the
first place. I never liked that, but, it was the only way I could
invoke the DHTML to round element corners using the "Nifty" technique
in such a way that I had determined the content was fully loaded into
the document DOM first before applying the "Nifty" manipulation of the
dialog content elements.
Cheers, Van
P.S. I'm taking a break for the SuperBowl now. Go Bears! :-)
_______________________________________________
Javawin mailing list
[email protected]
http://mail.xilinus.com/mailman/listinfo/javawin_xilinus.com
