Re: [Wicket-user] Wicket 2.0: Adding a component via ajax that contributes javascript (like AutoCompleteTextField) doesn't work correctly in Firefox

2006-10-17 Thread Matej Knopp
It fails to execute because the header javascript is executed before the elements are inserted to DOM. The solution would be not to render the javascript to head, question is how to determine whether header is being rendered or not. -Matej Caleb Land wrote: For some reason if the javascript

Re: [Wicket-user] Wicket 2.0: Adding a component via ajax that contributes javascript (like AutoCompleteTextField) doesn't work correctly in Firefox

2006-10-16 Thread Caleb Land
For some reason if the _javascript_ is rendered in the component's onRender(MarkupStream) method (as opposed to rendering the _javascript_ through a behavior) the _javascript_ is executed correctly. This is strange because when I look at the ajax debug window and compare the ajax responses of the

Re: [Wicket-user] Wicket 2.0: Adding a component via ajax that contributes javascript (like AutoCompleteTextField) doesn't work correctly in Firefox

2006-10-15 Thread Erik van Oosten
This is the same problem I reported a few days ago for Wicket 1.2.2. Igor wrote that it was already solved in th 1.x trunk. So maybe this is also the case for the 2.x trunk. Regards, Erik. Caleb Land schreef: When I add a component via ajax that contributes javascript to be executed

Re: [Wicket-user] Wicket 2.0: Adding a component via ajax that contributes javascript (like AutoCompleteTextField) doesn't work correctly in Firefox

2006-10-15 Thread Caleb Land
I'm using the 2.0 trunk. I think he was referring to the header contribution working when added via ajax. That does appear to work (the correct script reference is made to the autocomplete _javascript_ library), however the code that actually calls the library to create the field in the browser is

Re: [Wicket-user] Wicket 2.0: Adding a component via ajax that contributes javascript (like AutoCompleteTextField) doesn't work correctly in Firefox

2006-10-15 Thread Caleb Land
I've created the same testcase using wicket 1.2.2 and it works correctly in Firefox:http://www.granfalloon.com/~caleb/wicket-quickstart-1.2.2.zip I'm looking into the cause of it...On 10/15/06, Caleb Land [EMAIL PROTECTED] wrote: I'm using the 2.0 trunk. I think he was referring to the header

Re: [Wicket-user] Wicket 2.0: Adding a component via ajax that contributes javascript (like AutoCompleteTextField) doesn't work correctly in Firefox

2006-10-15 Thread Matej Knopp
Well, I'll try to look at it later today (or tomorrow). The problem is that firefox executes the script automatically, while in other browsers we need to call the scripts in the fragment manually. So I can't affect the order in which the scripts are bing called. I'll see what I can do about it.

Re: [Wicket-user] Wicket 2.0: Adding a component via ajax that contributes javascript (like AutoCompleteTextField) doesn't work correctly in Firefox

2006-10-15 Thread Caleb Land
Okay. I'm making this up as I go along, so this could be the worst idea ever, but what about scanning a component's response for script tag, putting the contents in the AjaxRequestTarget as _javascript_s, and removing the script tag from the normal component output? From my reading of the source

[Wicket-user] Wicket 2.0: Adding a component via ajax that contributes javascript (like AutoCompleteTextField) doesn't work correctly in Firefox

2006-10-14 Thread Caleb Land
When I add a component via ajax that contributes _javascript_ to be executed (like the AutoCompleteTextField from wicket-extensions) the _javascript_ is executed before the component elements are added to the page in Firefox ( 1.5.0.7). The same code works correctly in Safari, Opera, and IE7 (I