Re: [Wicket-user] Ajax autocompletion troubles

2006-11-03 Thread Erik van Oosten 
I verified it just now and it works!!!

Congratulations on solving this apparently difficult bug!

Thanks,
 Erik.

Matej Knopp schreef:
 Is that problem still present? Could you please check current svn too?

 -Matej

-- 
Erik van Oosten
http://www.day-to-day-stuff.blogspot.com/


-
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642
___
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user

Re: [Wicket-user] Ajax autocompletion troubles

2006-11-02 Thread Matej Knopp 
Can you please provide a test case?

Thanks.
-Matej

Erik van Oosten wrote:
 Hi,
 
 The release notes of 1.2.3 state that the Ajax header contributions 
 should be gone. Since the 1.2.3 release is still not in Ibiblio I just 
 upgraded (1 Oct, 11:00 CET) my copy of the 1.x branch. I triple checked 
 that I am actually working with that copy.
 
 Unfortunately there are still problems with autocompletion, both in IE 
 and FireFox. In my setup I have a AJAX-loaded panel that contains form 
 fields with autocompletion.
 
 --IE 6.0--
 In IE the autocompletion works, but each autocompletion handlers is 
 instantiated twice.
 When I look at the source (I use the Full source plugin), I see the 
 autocompletion js included inline in the page. Below that you see the 
 following:
 
 SCRIPT id=null src_=undefined!--/*--![CDATA[/*!--*/
 new 
 Wicket.AutoComplete('maincontent_searchform_form_formElements_2_inputfragment_formelement','/rbrb/app?wicket:interface=:1:maincontent:searchform:form:formElements:2:inputfragment:formelement:-1:IUnversionedBehaviorListenerwicket:behaviorId=0wicket:ignoreIfNotActive=true');
 /*--]]*//SCRIPT
 SCRIPT id=null src_=undefined!--/*--![CDATA[/*!--*/
 new 
 Wicket.AutoComplete('maincontent_searchform_form_formElements_3_inputfragment_formelement','/rbrb/app?wicket:interface=:1:maincontent:searchform:form:formElements:3:inputfragment:formelement:-1:IUnversionedBehaviorListenerwicket:behaviorId=0wicket:ignoreIfNotActive=true');
 /*--]]*//SCRIPT
 SCRIPT id=null src_=undefined!--/*--![CDATA[/*!--*/
 new 
 Wicket.AutoComplete('maincontent_searchform_form_formElements_4_inputfragment_formelement','/rbrb/app?wicket:interface=:1:maincontent:searchform:form:formElements:4:inputfragment:formelement:-1:IUnversionedBehaviorListenerwicket:behaviorId=0wicket:ignoreIfNotActive=true');
 /*--]]*//SCRIPT
 SCRIPT id=undefined src_=undefined!--/*--![CDATA[/*!--*/
 new 
 Wicket.AutoComplete('maincontent_searchform_form_formElements_2_inputfragment_formelement','/rbrb/app?wicket:interface=:1:maincontent:searchform:form:formElements:2:inputfragment:formelement:-1:IUnversionedBehaviorListenerwicket:behaviorId=0wicket:ignoreIfNotActive=true');
 /*--]]*//SCRIPT
 SCRIPT id=undefined src_=undefined!--/*--![CDATA[/*!--*/
 new 
 Wicket.AutoComplete('maincontent_searchform_form_formElements_3_inputfragment_formelement','/rbrb/app?wicket:interface=:1:maincontent:searchform:form:formElements:3:inputfragment:formelement:-1:IUnversionedBehaviorListenerwicket:behaviorId=0wicket:ignoreIfNotActive=true');
 /*--]]*//SCRIPT
 SCRIPT id=undefined src_=undefined!--/*--![CDATA[/*!--*/
 new 
 Wicket.AutoComplete('maincontent_searchform_form_formElements_4_inputfragment_formelement','/rbrb/app?wicket:interface=:1:maincontent:searchform:form:formElements:4:inputfragment:formelement:-1:IUnversionedBehaviorListenerwicket:behaviorId=0wicket:ignoreIfNotActive=true');
 /*--]]*//SCRIPT
 
 
 --FireFox 2.0--
 In FireFox the autocompletion only works after a submit of the form.
 After the first load of the panel (with Ajax) I also see autocompletion 
 js inline in the page header. Below that you see:
 
 script src_=undefined id=!--/*--![CDATA[/*!--*/
 new 
 Wicket.AutoComplete('maincontent_searchform_form_formElements_2_inputfragment_formelement','/rbrb/app?wicket:interface=:1:maincontent:searchform:form:formElements:2:inputfragment:formelement:-1:IUnversionedBehaviorListenerwicket:behaviorId=0wicket:ignoreIfNotActive=true');
 /*--]]*//scriptscript src_=undefined id=!--/*--![CDATA[/*!--*/
 new 
 Wicket.AutoComplete('maincontent_searchform_form_formElements_3_inputfragment_formelement','/rbrb/app?wicket:interface=:1:maincontent:searchform:form:formElements:3:inputfragment:formelement:-1:IUnversionedBehaviorListenerwicket:behaviorId=0wicket:ignoreIfNotActive=true');
 /*--]]*//scriptscript src_=undefined id=!--/*--![CDATA[/*!--*/
 new 
 Wicket.AutoComplete('maincontent_searchform_form_formElements_4_inputfragment_formelement','/rbrb/app?wicket:interface=:1:maincontent:searchform:form:formElements:4:inputfragment:formelement:-1:IUnversionedBehaviorListenerwicket:behaviorId=0wicket:ignoreIfNotActive=true');
 /*--]]*//script
 
 These pieces of javascript are unfortunately not being executed.
 Note that the id's are empty and there this weird src_ attribute. I am 
 sure how FireFox treats this. Also I wonder why the scripts are so 
 carefully commented. I guess that every browser that supports Ajax will 
 not need these comments.
 
 I tried to debug the load phase with FireBug. Unfortunately my 
 JavaScript is lacking way too much for this advanced stuff.
 
 Any help is greatly appreciated.
 
 Regards,
  Erik.
 
 
 -- 
 Erik van Oosten
 http://www.day-to-day-stuff.blogspot.com/
 
 
 
 
 -
 Using Tomcat but need to do more? Need to support web services, security?
 Get stuff done quickly with pre-integrated

Re: [Wicket-user] Ajax autocompletion troubles

2006-11-02 Thread Erik van Oosten 
Hi Matej,

You can download a quickstart here: 
https://omelet.zapto.org/ajaxtrouble.zip (3Mb).

Regards,
Erik.


Matej Knopp schreef:
 Can you please provide a test case?

 Thanks.
 -Matej

 Erik van Oosten wrote:
   
 Hi,

 The release notes of 1.2.3 state that the Ajax header contributions 
 should be gone. Since the 1.2.3 release is still not in Ibiblio I just 
 upgraded (1 Oct, 11:00 CET) my copy of the 1.x branch. I triple checked 
 that I am actually working with that copy.

 Unfortunately there are still problems with autocompletion, both in IE 
 and FireFox. In my setup I have a AJAX-loaded panel that contains form 
 fields with autocompletion.

 --IE 6.0--
 In IE the autocompletion works, but each autocompletion handlers is 
 instantiated twice.
 When I look at the source (I use the Full source plugin), I see the 
 autocompletion js included inline in the page. Below that you see the 
 following:

 SCRIPT id=null src_=undefined!--/*--![CDATA[/*!--*/
 new 
 Wicket.AutoComplete('maincontent_searchform_form_formElements_2_inputfragment_formelement','/rbrb/app?wicket:interface=:1:maincontent:searchform:form:formElements:2:inputfragment:formelement:-1:IUnversionedBehaviorListenerwicket:behaviorId=0wicket:ignoreIfNotActive=true');
 /*--]]*//SCRIPT
 SCRIPT id=null src_=undefined!--/*--![CDATA[/*!--*/
 new 
 Wicket.AutoComplete('maincontent_searchform_form_formElements_3_inputfragment_formelement','/rbrb/app?wicket:interface=:1:maincontent:searchform:form:formElements:3:inputfragment:formelement:-1:IUnversionedBehaviorListenerwicket:behaviorId=0wicket:ignoreIfNotActive=true');
 /*--]]*//SCRIPT
 SCRIPT id=null src_=undefined!--/*--![CDATA[/*!--*/
 new 
 Wicket.AutoComplete('maincontent_searchform_form_formElements_4_inputfragment_formelement','/rbrb/app?wicket:interface=:1:maincontent:searchform:form:formElements:4:inputfragment:formelement:-1:IUnversionedBehaviorListenerwicket:behaviorId=0wicket:ignoreIfNotActive=true');
 /*--]]*//SCRIPT
 SCRIPT id=undefined src_=undefined!--/*--![CDATA[/*!--*/
 new 
 Wicket.AutoComplete('maincontent_searchform_form_formElements_2_inputfragment_formelement','/rbrb/app?wicket:interface=:1:maincontent:searchform:form:formElements:2:inputfragment:formelement:-1:IUnversionedBehaviorListenerwicket:behaviorId=0wicket:ignoreIfNotActive=true');
 /*--]]*//SCRIPT
 SCRIPT id=undefined src_=undefined!--/*--![CDATA[/*!--*/
 new 
 Wicket.AutoComplete('maincontent_searchform_form_formElements_3_inputfragment_formelement','/rbrb/app?wicket:interface=:1:maincontent:searchform:form:formElements:3:inputfragment:formelement:-1:IUnversionedBehaviorListenerwicket:behaviorId=0wicket:ignoreIfNotActive=true');
 /*--]]*//SCRIPT
 SCRIPT id=undefined src_=undefined!--/*--![CDATA[/*!--*/
 new 
 Wicket.AutoComplete('maincontent_searchform_form_formElements_4_inputfragment_formelement','/rbrb/app?wicket:interface=:1:maincontent:searchform:form:formElements:4:inputfragment:formelement:-1:IUnversionedBehaviorListenerwicket:behaviorId=0wicket:ignoreIfNotActive=true');
 /*--]]*//SCRIPT


 --FireFox 2.0--
 In FireFox the autocompletion only works after a submit of the form.
 After the first load of the panel (with Ajax) I also see autocompletion 
 js inline in the page header. Below that you see:

 script src_=undefined id=!--/*--![CDATA[/*!--*/
 new 
 Wicket.AutoComplete('maincontent_searchform_form_formElements_2_inputfragment_formelement','/rbrb/app?wicket:interface=:1:maincontent:searchform:form:formElements:2:inputfragment:formelement:-1:IUnversionedBehaviorListenerwicket:behaviorId=0wicket:ignoreIfNotActive=true');
 /*--]]*//scriptscript src_=undefined id=!--/*--![CDATA[/*!--*/
 new 
 Wicket.AutoComplete('maincontent_searchform_form_formElements_3_inputfragment_formelement','/rbrb/app?wicket:interface=:1:maincontent:searchform:form:formElements:3:inputfragment:formelement:-1:IUnversionedBehaviorListenerwicket:behaviorId=0wicket:ignoreIfNotActive=true');
 /*--]]*//scriptscript src_=undefined id=!--/*--![CDATA[/*!--*/
 new 
 Wicket.AutoComplete('maincontent_searchform_form_formElements_4_inputfragment_formelement','/rbrb/app?wicket:interface=:1:maincontent:searchform:form:formElements:4:inputfragment:formelement:-1:IUnversionedBehaviorListenerwicket:behaviorId=0wicket:ignoreIfNotActive=true');
 /*--]]*//script

 These pieces of javascript are unfortunately not being executed.
 Note that the id's are empty and there this weird src_ attribute. I am 
 sure how FireFox treats this. Also I wonder why the scripts are so 
 carefully commented. I guess that every browser that supports Ajax will 
 not need these comments.

 I tried to debug the load phase with FireBug. Unfortunately my 
 JavaScript is lacking way too much for this advanced stuff.

 Any help is greatly appreciated.

 Regards,
  Erik.

-- 
Erik van Oosten
http://www.day-to-day-stuff.blogspot.com/


-
Using Tomcat but need to do more? Need to support web services,

Re: [Wicket-user] Ajax autocompletion troubles

2006-11-02 Thread Caleb Land 
This looks exactly like the problem I was having (the cause of which is, I believe WICKET-7).Check out this thread: 
http://www.nabble.com/Wicket-2.0%3A-Adding-a-component-via-ajax-that-contributes-_javascript_-%28like-AutoCompleteTextField%29-doesn%27t-work-correctly-in-Firefox-tf2445250.html#a6824693
On 11/2/06, Erik van Oosten [EMAIL PROTECTED] wrote:
Hi Matej,You can download a quickstart here:https://omelet.zapto.org/ajaxtrouble.zip (3Mb).Regards,Erik.Matej Knopp schreef:
 Can you please provide a test case? Thanks. -Matej Erik van Oosten wrote: Hi, The release notes of 1.2.3 state that the Ajax header contributions
 should be gone. Since the 1.2.3 release is still not in Ibiblio I just upgraded (1 Oct, 11:00 CET) my copy of the 1.x branch. I triple checked that I am actually working with that copy.
 Unfortunately there are still problems with autocompletion, both in IE and FireFox. In my setup I have a AJAX-loaded panel that contains form fields with autocompletion.
 --IE 6.0-- In IE the autocompletion works, but each autocompletion handlers is instantiated twice. When I look at the source (I use the Full source plugin), I see the
 autocompletion js included inline in the page. Below that you see the following: SCRIPT id=null src_=undefined!--/*--![CDATA[/*!--*/
 new Wicket.AutoComplete('maincontent_searchform_form_formElements_2_inputfragment_formelement','/rbrb/app?wicket:interface=:1:maincontent:searchform:form:formElements:2:inputfragment:formelement:-1:IUnversionedBehaviorListenerwicket:behaviorId=0wicket:ignoreIfNotActive=true');
 /*--]]*//SCRIPT SCRIPT id=null src_=undefined!--/*--![CDATA[/*!--*/ new Wicket.AutoComplete('maincontent_searchform_form_formElements_3_inputfragment_formelement','/rbrb/app?wicket:interface=:1:maincontent:searchform:form:formElements:3:inputfragment:formelement:-1:IUnversionedBehaviorListenerwicket:behaviorId=0wicket:ignoreIfNotActive=true');
 /*--]]*//SCRIPT SCRIPT id=null src_=undefined!--/*--![CDATA[/*!--*/ new Wicket.AutoComplete('maincontent_searchform_form_formElements_4_inputfragment_formelement','/rbrb/app?wicket:interface=:1:maincontent:searchform:form:formElements:4:inputfragment:formelement:-1:IUnversionedBehaviorListenerwicket:behaviorId=0wicket:ignoreIfNotActive=true');
 /*--]]*//SCRIPT SCRIPT id=undefined src_=undefined!--/*--![CDATA[/*!--*/ new Wicket.AutoComplete('maincontent_searchform_form_formElements_2_inputfragment_formelement','/rbrb/app?wicket:interface=:1:maincontent:searchform:form:formElements:2:inputfragment:formelement:-1:IUnversionedBehaviorListenerwicket:behaviorId=0wicket:ignoreIfNotActive=true');
 /*--]]*//SCRIPT SCRIPT id=undefined src_=undefined!--/*--![CDATA[/*!--*/ new Wicket.AutoComplete('maincontent_searchform_form_formElements_3_inputfragment_formelement','/rbrb/app?wicket:interface=:1:maincontent:searchform:form:formElements:3:inputfragment:formelement:-1:IUnversionedBehaviorListenerwicket:behaviorId=0wicket:ignoreIfNotActive=true');
 /*--]]*//SCRIPT SCRIPT id=undefined src_=undefined!--/*--![CDATA[/*!--*/ new Wicket.AutoComplete('maincontent_searchform_form_formElements_4_inputfragment_formelement','/rbrb/app?wicket:interface=:1:maincontent:searchform:form:formElements:4:inputfragment:formelement:-1:IUnversionedBehaviorListenerwicket:behaviorId=0wicket:ignoreIfNotActive=true');
 /*--]]*//SCRIPT --FireFox 2.0-- In FireFox the autocompletion only works after a submit of the form. After the first load of the panel (with Ajax) I also see autocompletion
 js inline in the page header. Below that you see: script src_=undefined id=!--/*--![CDATA[/*!--*/ new Wicket.AutoComplete
('maincontent_searchform_form_formElements_2_inputfragment_formelement','/rbrb/app?wicket:interface=:1:maincontent:searchform:form:formElements:2:inputfragment:formelement:-1:IUnversionedBehaviorListenerwicket:behaviorId=0wicket:ignoreIfNotActive=true');
 /*--]]*//scriptscript src_=undefined id=!--/*--![CDATA[/*!--*/ new Wicket.AutoComplete('maincontent_searchform_form_formElements_3_inputfragment_formelement','/rbrb/app?wicket:interface=:1:maincontent:searchform:form:formElements:3:inputfragment:formelement:-1:IUnversionedBehaviorListenerwicket:behaviorId=0wicket:ignoreIfNotActive=true');
 /*--]]*//scriptscript src_=undefined id=!--/*--![CDATA[/*!--*/ new Wicket.AutoComplete('maincontent_searchform_form_formElements_4_inputfragment_formelement','/rbrb/app?wicket:interface=:1:maincontent:searchform:form:formElements:4:inputfragment:formelement:-1:IUnversionedBehaviorListenerwicket:behaviorId=0wicket:ignoreIfNotActive=true');
 /*--]]*//script These pieces of _javascript_ are unfortunately not being executed. Note that the id's are empty and there this weird src_ attribute. I am
 sure how FireFox treats this. Also I wonder why the scripts are so carefully commented. I guess that every browser that supports Ajax will not need these comments. I tried to debug the load phase with FireBug. Unfortunately my
 _javascript_ is lacking way too much for this advanced

Re: [Wicket-user] Ajax autocompletion troubles

2006-11-02 Thread Matej Knopp 
Thanks for the testcase. Can you please check if the current svn (1.x) 
solves your problem? (It solved the testcase).

-Matej

Erik van Oosten wrote:
 Hi Matej,
 
 You can download a quickstart here: 
 https://omelet.zapto.org/ajaxtrouble.zip (3Mb).
 
 Regards,
 Erik.
 
 
 Matej Knopp schreef:
 Can you please provide a test case?

 Thanks.
 -Matej

 Erik van Oosten wrote:
   
 Hi,

 The release notes of 1.2.3 state that the Ajax header contributions 
 should be gone. Since the 1.2.3 release is still not in Ibiblio I just 
 upgraded (1 Oct, 11:00 CET) my copy of the 1.x branch. I triple checked 
 that I am actually working with that copy.

 Unfortunately there are still problems with autocompletion, both in IE 
 and FireFox. In my setup I have a AJAX-loaded panel that contains form 
 fields with autocompletion.

 --IE 6.0--
 In IE the autocompletion works, but each autocompletion handlers is 
 instantiated twice.
 When I look at the source (I use the Full source plugin), I see the 
 autocompletion js included inline in the page. Below that you see the 
 following:

 SCRIPT id=null src_=undefined!--/*--![CDATA[/*!--*/
 new 
 Wicket.AutoComplete('maincontent_searchform_form_formElements_2_inputfragment_formelement','/rbrb/app?wicket:interface=:1:maincontent:searchform:form:formElements:2:inputfragment:formelement:-1:IUnversionedBehaviorListenerwicket:behaviorId=0wicket:ignoreIfNotActive=true');
 /*--]]*//SCRIPT
 SCRIPT id=null src_=undefined!--/*--![CDATA[/*!--*/
 new 
 Wicket.AutoComplete('maincontent_searchform_form_formElements_3_inputfragment_formelement','/rbrb/app?wicket:interface=:1:maincontent:searchform:form:formElements:3:inputfragment:formelement:-1:IUnversionedBehaviorListenerwicket:behaviorId=0wicket:ignoreIfNotActive=true');
 /*--]]*//SCRIPT
 SCRIPT id=null src_=undefined!--/*--![CDATA[/*!--*/
 new 
 Wicket.AutoComplete('maincontent_searchform_form_formElements_4_inputfragment_formelement','/rbrb/app?wicket:interface=:1:maincontent:searchform:form:formElements:4:inputfragment:formelement:-1:IUnversionedBehaviorListenerwicket:behaviorId=0wicket:ignoreIfNotActive=true');
 /*--]]*//SCRIPT
 SCRIPT id=undefined src_=undefined!--/*--![CDATA[/*!--*/
 new 
 Wicket.AutoComplete('maincontent_searchform_form_formElements_2_inputfragment_formelement','/rbrb/app?wicket:interface=:1:maincontent:searchform:form:formElements:2:inputfragment:formelement:-1:IUnversionedBehaviorListenerwicket:behaviorId=0wicket:ignoreIfNotActive=true');
 /*--]]*//SCRIPT
 SCRIPT id=undefined src_=undefined!--/*--![CDATA[/*!--*/
 new 
 Wicket.AutoComplete('maincontent_searchform_form_formElements_3_inputfragment_formelement','/rbrb/app?wicket:interface=:1:maincontent:searchform:form:formElements:3:inputfragment:formelement:-1:IUnversionedBehaviorListenerwicket:behaviorId=0wicket:ignoreIfNotActive=true');
 /*--]]*//SCRIPT
 SCRIPT id=undefined src_=undefined!--/*--![CDATA[/*!--*/
 new 
 Wicket.AutoComplete('maincontent_searchform_form_formElements_4_inputfragment_formelement','/rbrb/app?wicket:interface=:1:maincontent:searchform:form:formElements:4:inputfragment:formelement:-1:IUnversionedBehaviorListenerwicket:behaviorId=0wicket:ignoreIfNotActive=true');
 /*--]]*//SCRIPT


 --FireFox 2.0--
 In FireFox the autocompletion only works after a submit of the form.
 After the first load of the panel (with Ajax) I also see autocompletion 
 js inline in the page header. Below that you see:

 script src_=undefined id=!--/*--![CDATA[/*!--*/
 new 
 Wicket.AutoComplete('maincontent_searchform_form_formElements_2_inputfragment_formelement','/rbrb/app?wicket:interface=:1:maincontent:searchform:form:formElements:2:inputfragment:formelement:-1:IUnversionedBehaviorListenerwicket:behaviorId=0wicket:ignoreIfNotActive=true');
 /*--]]*//scriptscript src_=undefined 
 id=!--/*--![CDATA[/*!--*/
 new 
 Wicket.AutoComplete('maincontent_searchform_form_formElements_3_inputfragment_formelement','/rbrb/app?wicket:interface=:1:maincontent:searchform:form:formElements:3:inputfragment:formelement:-1:IUnversionedBehaviorListenerwicket:behaviorId=0wicket:ignoreIfNotActive=true');
 /*--]]*//scriptscript src_=undefined 
 id=!--/*--![CDATA[/*!--*/
 new 
 Wicket.AutoComplete('maincontent_searchform_form_formElements_4_inputfragment_formelement','/rbrb/app?wicket:interface=:1:maincontent:searchform:form:formElements:4:inputfragment:formelement:-1:IUnversionedBehaviorListenerwicket:behaviorId=0wicket:ignoreIfNotActive=true');
 /*--]]*//script

 These pieces of javascript are unfortunately not being executed.
 Note that the id's are empty and there this weird src_ attribute. I am 
 sure how FireFox treats this. Also I wonder why the scripts are so 
 carefully commented. I guess that every browser that supports Ajax will 
 not need these comments.

 I tried to debug the load phase with FireBug. Unfortunately my 
 JavaScript is lacking way too much for this advanced stuff.

 Any help is greatly appreciated.

 Regards,
  Erik.

Re: [Wicket-user] Ajax autocompletion troubles

2006-11-02 Thread Matej Knopp 
oh, and don't forget to evict the javascript from browser cache ;-)

Matej Knopp wrote:
 Thanks for the testcase. Can you please check if the current svn (1.x) 
 solves your problem? (It solved the testcase).
 
 -Matej
 
 Erik van Oosten wrote:
 Hi Matej,

 You can download a quickstart here: 
 https://omelet.zapto.org/ajaxtrouble.zip (3Mb).

 Regards,
 Erik.


 Matej Knopp schreef:
 Can you please provide a test case?

 Thanks.
 -Matej

 Erik van Oosten wrote:
   
 Hi,

 The release notes of 1.2.3 state that the Ajax header contributions 
 should be gone. Since the 1.2.3 release is still not in Ibiblio I just 
 upgraded (1 Oct, 11:00 CET) my copy of the 1.x branch. I triple checked 
 that I am actually working with that copy.

 Unfortunately there are still problems with autocompletion, both in IE 
 and FireFox. In my setup I have a AJAX-loaded panel that contains form 
 fields with autocompletion.

 --IE 6.0--
 In IE the autocompletion works, but each autocompletion handlers is 
 instantiated twice.
 When I look at the source (I use the Full source plugin), I see the 
 autocompletion js included inline in the page. Below that you see the 
 following:

 SCRIPT id=null src_=undefined!--/*--![CDATA[/*!--*/
 new 
 Wicket.AutoComplete('maincontent_searchform_form_formElements_2_inputfragment_formelement','/rbrb/app?wicket:interface=:1:maincontent:searchform:form:formElements:2:inputfragment:formelement:-1:IUnversionedBehaviorListenerwicket:behaviorId=0wicket:ignoreIfNotActive=true');
 /*--]]*//SCRIPT
 SCRIPT id=null src_=undefined!--/*--![CDATA[/*!--*/
 new 
 Wicket.AutoComplete('maincontent_searchform_form_formElements_3_inputfragment_formelement','/rbrb/app?wicket:interface=:1:maincontent:searchform:form:formElements:3:inputfragment:formelement:-1:IUnversionedBehaviorListenerwicket:behaviorId=0wicket:ignoreIfNotActive=true');
 /*--]]*//SCRIPT
 SCRIPT id=null src_=undefined!--/*--![CDATA[/*!--*/
 new 
 Wicket.AutoComplete('maincontent_searchform_form_formElements_4_inputfragment_formelement','/rbrb/app?wicket:interface=:1:maincontent:searchform:form:formElements:4:inputfragment:formelement:-1:IUnversionedBehaviorListenerwicket:behaviorId=0wicket:ignoreIfNotActive=true');
 /*--]]*//SCRIPT
 SCRIPT id=undefined src_=undefined!--/*--![CDATA[/*!--*/
 new 
 Wicket.AutoComplete('maincontent_searchform_form_formElements_2_inputfragment_formelement','/rbrb/app?wicket:interface=:1:maincontent:searchform:form:formElements:2:inputfragment:formelement:-1:IUnversionedBehaviorListenerwicket:behaviorId=0wicket:ignoreIfNotActive=true');
 /*--]]*//SCRIPT
 SCRIPT id=undefined src_=undefined!--/*--![CDATA[/*!--*/
 new 
 Wicket.AutoComplete('maincontent_searchform_form_formElements_3_inputfragment_formelement','/rbrb/app?wicket:interface=:1:maincontent:searchform:form:formElements:3:inputfragment:formelement:-1:IUnversionedBehaviorListenerwicket:behaviorId=0wicket:ignoreIfNotActive=true');
 /*--]]*//SCRIPT
 SCRIPT id=undefined src_=undefined!--/*--![CDATA[/*!--*/
 new 
 Wicket.AutoComplete('maincontent_searchform_form_formElements_4_inputfragment_formelement','/rbrb/app?wicket:interface=:1:maincontent:searchform:form:formElements:4:inputfragment:formelement:-1:IUnversionedBehaviorListenerwicket:behaviorId=0wicket:ignoreIfNotActive=true');
 /*--]]*//SCRIPT


 --FireFox 2.0--
 In FireFox the autocompletion only works after a submit of the form.
 After the first load of the panel (with Ajax) I also see autocompletion 
 js inline in the page header. Below that you see:

 script src_=undefined id=!--/*--![CDATA[/*!--*/
 new 
 Wicket.AutoComplete('maincontent_searchform_form_formElements_2_inputfragment_formelement','/rbrb/app?wicket:interface=:1:maincontent:searchform:form:formElements:2:inputfragment:formelement:-1:IUnversionedBehaviorListenerwicket:behaviorId=0wicket:ignoreIfNotActive=true');
 /*--]]*//scriptscript src_=undefined 
 id=!--/*--![CDATA[/*!--*/
 new 
 Wicket.AutoComplete('maincontent_searchform_form_formElements_3_inputfragment_formelement','/rbrb/app?wicket:interface=:1:maincontent:searchform:form:formElements:3:inputfragment:formelement:-1:IUnversionedBehaviorListenerwicket:behaviorId=0wicket:ignoreIfNotActive=true');
 /*--]]*//scriptscript src_=undefined 
 id=!--/*--![CDATA[/*!--*/
 new 
 Wicket.AutoComplete('maincontent_searchform_form_formElements_4_inputfragment_formelement','/rbrb/app?wicket:interface=:1:maincontent:searchform:form:formElements:4:inputfragment:formelement:-1:IUnversionedBehaviorListenerwicket:behaviorId=0wicket:ignoreIfNotActive=true');
 /*--]]*//script

 These pieces of javascript are unfortunately not being executed.
 Note that the id's are empty and there this weird src_ attribute. I am 
 sure how FireFox treats this. Also I wonder why the scripts are so 
 carefully commented. I guess that every browser that supports Ajax will 
 not need these comments.

 I tried to debug the load phase with FireBug. Unfortunately my 
 JavaScript is lacking way too much for this advanced stuff.

 Any

Re: [Wicket-user] Ajax autocompletion troubles

2006-11-02 Thread Matej Knopp 
Is that problem still present? Could you please check current svn too?

-Matej

Caleb Land wrote:
 This looks exactly like the problem I was having (the cause of which is, 
 I believe WICKET-7).
 
 Check out this thread: 
 http://www.nabble.com/Wicket-2.0%3A-Adding-a-component-via-ajax-that-contributes-javascript-%28like-AutoCompleteTextField%29-doesn%27t-work-correctly-in-Firefox-tf2445250.html#a6824693
  
 http://www.nabble.com/Wicket-2.0%253A-Adding-a-component-via-ajax-that-contributes-javascript-%2528like-AutoCompleteTextField%2529-doesn%2527t-work-correctly-in-Firefox-tf2445250.html#a6824693
 
 On 11/2/06, *Erik van Oosten* [EMAIL PROTECTED] 
 mailto:[EMAIL PROTECTED] wrote:
 
 Hi Matej,
 
 You can download a quickstart here:
 https://omelet.zapto.org/ajaxtrouble.zip (3Mb).
 
 Regards,
 Erik.
 
 
 Matej Knopp schreef:
   Can you please provide a test case?
  
   Thanks.
   -Matej
  
   Erik van Oosten wrote:
  
   Hi,
  
   The release notes of 1.2.3 state that the Ajax header contributions
   should be gone. Since the 1.2.3 release is still not in Ibiblio
 I just
   upgraded (1 Oct, 11:00 CET) my copy of the 1.x branch. I triple
 checked
   that I am actually working with that copy.
  
   Unfortunately there are still problems with autocompletion, both
 in IE
   and FireFox. In my setup I have a AJAX-loaded panel that
 contains form
   fields with autocompletion.
  
   --IE 6.0--
   In IE the autocompletion works, but each autocompletion handlers is
   instantiated twice.
   When I look at the source (I use the Full source plugin), I see the
   autocompletion js included inline in the page. Below that you
 see the
   following:
  
   SCRIPT id=null src_=undefined!--/*--![CDATA[/*!--*/
   new
 
 Wicket.AutoComplete('maincontent_searchform_form_formElements_2_inputfragment_formelement','/rbrb/app?wicket:interface=:1:maincontent:searchform:form:formElements:2:inputfragment:formelement:-1:IUnversionedBehaviorListenerwicket:behaviorId=0wicket:ignoreIfNotActive=true');
 
   /*--]]*//SCRIPT
   SCRIPT id=null src_=undefined!--/*--![CDATA[/*!--*/
   new
 
 Wicket.AutoComplete('maincontent_searchform_form_formElements_3_inputfragment_formelement','/rbrb/app?wicket:interface=:1:maincontent:searchform:form:formElements:3:inputfragment:formelement:-1:IUnversionedBehaviorListenerwicket:behaviorId=0wicket:ignoreIfNotActive=true');
 
   /*--]]*//SCRIPT
   SCRIPT id=null src_=undefined!--/*--![CDATA[/*!--*/
   new
 
 Wicket.AutoComplete('maincontent_searchform_form_formElements_4_inputfragment_formelement','/rbrb/app?wicket:interface=:1:maincontent:searchform:form:formElements:4:inputfragment:formelement:-1:IUnversionedBehaviorListenerwicket:behaviorId=0wicket:ignoreIfNotActive=true');
 
   /*--]]*//SCRIPT
   SCRIPT id=undefined src_=undefined!--/*--![CDATA[/*!--*/
   new
 
 Wicket.AutoComplete('maincontent_searchform_form_formElements_2_inputfragment_formelement','/rbrb/app?wicket:interface=:1:maincontent:searchform:form:formElements:2:inputfragment:formelement:-1:IUnversionedBehaviorListenerwicket:behaviorId=0wicket:ignoreIfNotActive=true');
 
   /*--]]*//SCRIPT
   SCRIPT id=undefined src_=undefined!--/*--![CDATA[/*!--*/
   new
 
 Wicket.AutoComplete('maincontent_searchform_form_formElements_3_inputfragment_formelement','/rbrb/app?wicket:interface=:1:maincontent:searchform:form:formElements:3:inputfragment:formelement:-1:IUnversionedBehaviorListenerwicket:behaviorId=0wicket:ignoreIfNotActive=true');
 
   /*--]]*//SCRIPT
   SCRIPT id=undefined src_=undefined!--/*--![CDATA[/*!--*/
   new
 
 Wicket.AutoComplete('maincontent_searchform_form_formElements_4_inputfragment_formelement','/rbrb/app?wicket:interface=:1:maincontent:searchform:form:formElements:4:inputfragment:formelement:-1:IUnversionedBehaviorListenerwicket:behaviorId=0wicket:ignoreIfNotActive=true');
 
   /*--]]*//SCRIPT
  
  
   --FireFox 2.0--
   In FireFox the autocompletion only works after a submit of the form.
   After the first load of the panel (with Ajax) I also see
 autocompletion
   js inline in the page header. Below that you see:
  
   script src_=undefined id=!--/*--![CDATA[/*!--*/
   new Wicket.AutoComplete
 
 ('maincontent_searchform_form_formElements_2_inputfragment_formelement','/rbrb/app?wicket:interface=:1:maincontent:searchform:form:formElements:2:inputfragment:formelement:-1:IUnversionedBehaviorListenerwicket:behaviorId=0wicket:ignoreIfNotActive=true');
 
   /*--]]*//scriptscript src_=undefined
 id=!--/*--![CDATA[/*!--*/
   new

Re: [Wicket-user] Ajax autocompletion troubles

2006-11-02 Thread Caleb Land 
On 11/2/06, Matej Knopp [EMAIL PROTECTED] wrote:
Is that problem still present? Could you please check current svn too?It appears to work on my end with Wicket 2. Thanks!
-MatejCaleb Land wrote: This looks exactly like the problem I was having (the cause of which is, I believe WICKET-7). Check out this thread: 
http://www.nabble.com/Wicket-2.0%3A-Adding-a-component-via-ajax-that-contributes-_javascript_-%28like-AutoCompleteTextField%29-doesn%27t-work-correctly-in-Firefox-tf2445250.html#a6824693 
http://www.nabble.com/Wicket-2.0%253A-Adding-a-component-via-ajax-that-contributes-_javascript_-%2528like-AutoCompleteTextField%2529-doesn%2527t-work-correctly-in-Firefox-tf2445250.html#a6824693 On 11/2/06, *Erik van Oosten* 
[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: Hi Matej, You can download a quickstart here:
 https://omelet.zapto.org/ajaxtrouble.zip (3Mb). Regards, Erik. Matej Knopp schreef: Can you please provide a test case?
 Thanks. -Matej Erik van Oosten wrote: Hi, The release notes of 
1.2.3 state that the Ajax header contributions should be gone. Since the 1.2.3 release is still not in Ibiblio I just upgraded (1 Oct, 11:00 CET) my copy of the 1.x branch. I triple
 checked that I am actually working with that copy. Unfortunately there are still problems with autocompletion, both in IE and FireFox. In my setup I have a AJAX-loaded panel that
 contains form fields with autocompletion. --IE 6.0-- In IE the autocompletion works, but each autocompletion handlers is
 instantiated twice. When I look at the source (I use the Full source plugin), I see the autocompletion js included inline in the page. Below that you see the
 following: SCRIPT id=null src_=undefined!--/*--![CDATA[/*!--*/ new Wicket.AutoComplete
('maincontent_searchform_form_formElements_2_inputfragment_formelement','/rbrb/app?wicket:interface=:1:maincontent:searchform:form:formElements:2:inputfragment:formelement:-1:IUnversionedBehaviorListenerwicket:behaviorId=0wicket:ignoreIfNotActive=true');
 /*--]]*//SCRIPT SCRIPT id=null src_=undefined!--/*--![CDATA[/*!--*/ new Wicket.AutoComplete
('maincontent_searchform_form_formElements_3_inputfragment_formelement','/rbrb/app?wicket:interface=:1:maincontent:searchform:form:formElements:3:inputfragment:formelement:-1:IUnversionedBehaviorListenerwicket:behaviorId=0wicket:ignoreIfNotActive=true');
 /*--]]*//SCRIPT SCRIPT id=null src_=undefined!--/*--![CDATA[/*!--*/ new Wicket.AutoComplete
('maincontent_searchform_form_formElements_4_inputfragment_formelement','/rbrb/app?wicket:interface=:1:maincontent:searchform:form:formElements:4:inputfragment:formelement:-1:IUnversionedBehaviorListenerwicket:behaviorId=0wicket:ignoreIfNotActive=true');
 /*--]]*//SCRIPT SCRIPT id=undefined src_=undefined!--/*--![CDATA[/*!--*/ new Wicket.AutoComplete
('maincontent_searchform_form_formElements_2_inputfragment_formelement','/rbrb/app?wicket:interface=:1:maincontent:searchform:form:formElements:2:inputfragment:formelement:-1:IUnversionedBehaviorListenerwicket:behaviorId=0wicket:ignoreIfNotActive=true');
 /*--]]*//SCRIPT SCRIPT id=undefined src_=undefined!--/*--![CDATA[/*!--*/ new Wicket.AutoComplete
('maincontent_searchform_form_formElements_3_inputfragment_formelement','/rbrb/app?wicket:interface=:1:maincontent:searchform:form:formElements:3:inputfragment:formelement:-1:IUnversionedBehaviorListenerwicket:behaviorId=0wicket:ignoreIfNotActive=true');
 /*--]]*//SCRIPT SCRIPT id=undefined src_=undefined!--/*--![CDATA[/*!--*/ new Wicket.AutoComplete
('maincontent_searchform_form_formElements_4_inputfragment_formelement','/rbrb/app?wicket:interface=:1:maincontent:searchform:form:formElements:4:inputfragment:formelement:-1:IUnversionedBehaviorListenerwicket:behaviorId=0wicket:ignoreIfNotActive=true');
 /*--]]*//SCRIPT --FireFox 2.0-- In FireFox the autocompletion only works after a submit of the form.
 After the first load of the panel (with Ajax) I also see autocompletion js inline in the page header. Below that you see: script src_=undefined id=!--/*--![CDATA[/*!--*/
 new Wicket.AutoComplete ('maincontent_searchform_form_formElements_2_inputfragment_formelement','/rbrb/app?wicket:interface=:1:maincontent:searchform:form:formElements:2:inputfragment:formelement:-1:IUnversionedBehaviorListenerwicket:behaviorId=0wicket:ignoreIfNotActive=true');
 /*--]]*//scriptscript src_=undefined id=!--/*--![CDATA[/*!--*/ new Wicket.AutoComplete
('maincontent_searchform_form_formElements_3_inputfragment_formelement','/rbrb/app?wicket:interface=:1:maincontent:searchform:form:formElements:3:inputfragment:formelement:-1:IUnversionedBehaviorListenerwicket:behaviorId=0wicket:ignoreIfNotActive=true');
 /*--]]*//scriptscript src_=undefined id=!--/*--![CDATA[/*!--*/ new Wicket.AutoComplete
('maincontent_searchform_form_formElements_4_inputfragment_formelement','/rbrb/app?wicket:interface=:1:maincontent:searchform:form:formElements:4:inputfragment:formelement:-1:IUnversionedBehaviorListenerwicket:behaviorId=0wicket:ignoreIfNotActive=true');

Re: [Wicket-user] Ajax autocompletion troubles

2006-11-02 Thread Erik van Oosten 
I used the 1.x branch from svn at October 1, around 14:00 CET.
Do you want me to check today's svn?

  Erik.

Matej Knopp schreef:
 Is that problem still present? Could you please check current svn too?

 -Matej

   

-- 
Erik van Oosten
http://www.day-to-day-stuff.blogspot.com/


-
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642
___
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user

Re: [Wicket-user] Ajax autocompletion troubles

2006-11-02 Thread Erik van Oosten 
I just did an update and I see that relevant files have been changed. 
I'll try immediately.

Thanks,
 Erik.

Erik van Oosten schreef:
 I used the 1.x branch from svn at October 1, around 14:00 CET.
 Do you want me to check today's svn?

   Erik.

 Matej Knopp schreef:
   
 Is that problem still present? Could you please check current svn too?

 -Matej
 

-- 
Erik van Oosten
http://www.day-to-day-stuff.blogspot.com/


-
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642
___
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user

Re: [Wicket-user] Ajax autocompletion troubles

2006-11-01 Thread Caleb Land 
Check out this bug:http://issues.apache.org/jira/browse/WICKET-7For now I just converted all of my component swapping links to normal links instead of ajax ones. I'd try to fix that bug myself, but from the discussions on this mailing list about it, it seems like a low level Wicket refactor is required to fix it.
On 11/1/06, Erik van Oosten [EMAIL PROTECTED] wrote:



  


Hi,

The release notes of 1.2.3 state that the Ajax header contributions
should be gone. Since the 1.2.3 release is still not in Ibiblio I just
upgraded (1 Oct, 11:00 CET) my copy of the 1.x branch. I triple checked
that I am actually working with that copy.

Unfortunately there are still problems with autocompletion, both in IE
and FireFox. In my setup I have a AJAX-loaded panel that contains form
fields with autocompletion.

--IE 6.0--
In IE the autocompletion works, but each autocompletion handlers is
instantiated twice.
When I look at the source (I use the Full source plugin), I see the
autocompletion js included inline in the page. Below that you see the
following:

SCRIPT id=null src_=undefined!--/*--![CDATA[/*!--*/new Wicket.AutoComplete('maincontent_searchform_form_formElements_2_inputfragment_formelement','/rbrb/app?wicket:interface=:1:maincontent:searchform:form:formElements:2:inputfragment:formelement:-1:IUnversionedBehaviorListenerwicket:behaviorId=0wicket:ignoreIfNotActive=true');
/*--]]*//SCRIPTSCRIPT id=null src_=undefined!--/*--![CDATA[/*!--*/new Wicket.AutoComplete('maincontent_searchform_form_formElements_3_inputfragment_formelement','/rbrb/app?wicket:interface=:1:maincontent:searchform:form:formElements:3:inputfragment:formelement:-1:IUnversionedBehaviorListenerwicket:behaviorId=0wicket:ignoreIfNotActive=true');
/*--]]*//SCRIPTSCRIPT id=null src_=undefined!--/*--![CDATA[/*!--*/new Wicket.AutoComplete('maincontent_searchform_form_formElements_4_inputfragment_formelement','/rbrb/app?wicket:interface=:1:maincontent:searchform:form:formElements:4:inputfragment:formelement:-1:IUnversionedBehaviorListenerwicket:behaviorId=0wicket:ignoreIfNotActive=true');
/*--]]*//SCRIPTSCRIPT id=undefined src_=undefined!--/*--![CDATA[/*!--*/new Wicket.AutoComplete('maincontent_searchform_form_formElements_2_inputfragment_formelement','/rbrb/app?wicket:interface=:1:maincontent:searchform:form:formElements:2:inputfragment:formelement:-1:IUnversionedBehaviorListenerwicket:behaviorId=0wicket:ignoreIfNotActive=true');
/*--]]*//SCRIPTSCRIPT id=undefined src_=undefined!--/*--![CDATA[/*!--*/new Wicket.AutoComplete('maincontent_searchform_form_formElements_3_inputfragment_formelement','/rbrb/app?wicket:interface=:1:maincontent:searchform:form:formElements:3:inputfragment:formelement:-1:IUnversionedBehaviorListenerwicket:behaviorId=0wicket:ignoreIfNotActive=true');
/*--]]*//SCRIPTSCRIPT id=undefined src_=undefined!--/*--![CDATA[/*!--*/new Wicket.AutoComplete('maincontent_searchform_form_formElements_4_inputfragment_formelement','/rbrb/app?wicket:interface=:1:maincontent:searchform:form:formElements:4:inputfragment:formelement:-1:IUnversionedBehaviorListenerwicket:behaviorId=0wicket:ignoreIfNotActive=true');
/*--]]*//SCRIPT

--FireFox 2.0--
In FireFox the autocompletion only works after a submit of the form.
After the first load of the panel (with Ajax) I also see autocompletion
js inline in the page header. Below that you see:
script src_=undefined id=!--/*--![CDATA[/*!--*/new Wicket.AutoComplete('maincontent_searchform_form_formElements_2_inputfragment_formelement','/rbrb/app?wicket:interface=:1:maincontent:searchform:form:formElements:2:inputfragment:formelement:-1:IUnversionedBehaviorListenerwicket:behaviorId=0wicket:ignoreIfNotActive=true');
/*--]]*//scriptscript src_=undefined id=!--/*--![CDATA[/*!--*/new Wicket.AutoComplete('maincontent_searchform_form_formElements_3_inputfragment_formelement','/rbrb/app?wicket:interface=:1:maincontent:searchform:form:formElements:3:inputfragment:formelement:-1:IUnversionedBehaviorListenerwicket:behaviorId=0wicket:ignoreIfNotActive=true');
/*--]]*//scriptscript src_=undefined id=!--/*--![CDATA[/*!--*/new Wicket.AutoComplete('maincontent_searchform_form_formElements_4_inputfragment_formelement','/rbrb/app?wicket:interface=:1:maincontent:searchform:form:formElements:4:inputfragment:formelement:-1:IUnversionedBehaviorListenerwicket:behaviorId=0wicket:ignoreIfNotActive=true');
/*--]]*//script
These pieces of _javascript_ are unfortunately not being executed.
Note that the id's are empty and there this weird src_ attribute. I
am sure how FireFox treats this. Also I wonder why the scripts are so
carefully commented. I guess that every browser that supports Ajax will
not need these comments.

I tried to debug the load phase with FireBug. Unfortunately my
_javascript_ is lacking way too much for this advanced stuff.

Any help is greatly appreciated.

Regards,
 Erik.


-- Erik van Oostenhttp://www.day-to-day-stuff.blogspot.com/



-Using Tomcat but