RE: AjaxFormComponentUpdatingBehavior not triggering ListChoice model update in Firefox in Wicket 7.9.0

[Chris Colman]

Dang! I thought the app was doing a 

continueToOriginalDestination();

to return from the login page to the home page at "/" but it wasn't so there's 
no problem with continueToOriginalDestination().

It was actually doing a setResponse(new HomePage()); from a 
the LogonPage that had no @MountPath annotation.

So I think the issue is a non issue - should always be using 
continueToOriginalDestination() to return from a login page to the page that 
requested login.

The issue only seems to occur when browser hits the page mounted at "/" and 
then gets redirected to intercept page that has no mount path (so browser URL 
isn't changed) and then instead of returning using 
continueToOriginalDestination it does a direct setResponse(new HomePage()); to 
go the page mounted at "/".

Only in that scenario does the form action attribute end up with ..? which 
FireFox doesn't seem to handle.

So by specifying a mount path for the login page or by using (the proper 
approach) continueToOriginalDestination() to return after intercept then the 
problem does not occur.

> -Original Message-
> From: Chris Colman [mailto:chr...@stepaheadsoftware.com]
> Sent: Wednesday, 11 October 2017 9:59 PM
> To: users@wicket.apache.org
> Subject: RE: AjaxFormComponentUpdatingBehavior not triggering ListChoice
> model update in Firefox in Wicket 7.9.0
> 
> Found it
> 
> It seems FireFox does have an issue with the actions that start with ..?
> 
> The page I was going to (localhost/myapp) had a mount path at "/"
> 
> i.e.
> 
> @MountPath(value = "/", alt = "/home")
> 
> Now this mount path annotation was also in the test app that didn't
> exhibit the problem but (yes!) but the main app has a test for
> authenticated user with redirect:
> 
> // redirect to authenticate page if we don't have an authenticated user
> redirectToInterceptPage(new AuthenticatePage());
> 
> The quickstart does not check for authentication so no redirect.
> 
> The problem goes away in Firefox if I change the mountpath to anything but
> "/" eg.,
> 
> @MountPath(value = "/blah", alt = "/home")
> 
> So my theory is that an action URL generated for a form in a page mounted
> at '/' is correct (./?) if the page is accessed directly without a
> redirectToInterceptPage.
> 
> but when the action URL is generated after a "continue after intercept" to
> a page that is mounted at '/' then the action URL is generated with the
> ..? prefix instead of ./?.
> 
> While Chrome can handle ..? it appears Firefox does not but works fine
> with ./?
> 
> 
> 
> > -Original Message-
> > From: Chris Colman [mailto:chr...@stepaheadsoftware.com]
> > Sent: Wednesday, 11 October 2017 9:29 PM
> > To: users@wicket.apache.org
> > Subject: RE: AjaxFormComponentUpdatingBehavior not triggering ListChoice
> > model update in Firefox in Wicket 7.9.0
> >
> > I found an interesting difference between the quickstart that works and
> > the app that doesn't work in FF:
> >
> > The action parameter of the form is generated with a .. prefix instead
> of
> > ./
> >
> > So in the app that doesn't work:
> >
> > The form's action attribute is defined as:
> >
> > action="..?32-1.IFormSubmitListener-form"
> >
> > and in the app that does work it is defined as:
> >
> > action="./?0-1.IFormSubmitListener-form"
> >
> > The AJAX event handlers defined at the end of the page correspond to
> > whatever was generated above.
> >
> > The ..? form is generated in both Chrome and FireFox. Perhaps Firefox
> > doesn't handle this ..? as well as Chrome does.
> >
> > Is ..? a legal URL path?
> >
> > To test this theory I could force the real app to generate a ./? URL
> > instead of ..?
> >
> > Any idea how I could do that?
> >
> >
> > > -Original Message-
> > > From: Korbinian Bachl [mailto:korbinian.ba...@whiskyworld.de]
> > > Sent: Wednesday, 11 October 2017 7:12 PM
> > > To: users@wicket.apache.org
> > > Subject: Re: AjaxFormComponentUpdatingBehavior not triggering
> ListChoice
> > > model update in Firefox in Wicket 7.9.0
> > >
> > > Is there any kind of defer or async on any of these JS script
> resources?
> > > Maybe you want to publish the quickstart?
> > >
> > > - Ursprüngliche Mail -
> > > > Von: "Chris Colman" 
> > > > An: users@wicket.apache.org
> > > > Gesendet: Mittwoch, 11. Oktober 2017 10:06:23
> > > > Betreff: RE: AjaxFormComponentUpdatingBehavior not triggering
> > ListChoice
> > > model update in Firefox in Wicket 7.9.0
> > >
> > > > The cut down app that works fine in FireFox also has both jquery.js
> > and
> > > > bootstrap.js so this probably means that it's ok to have both of
> these
> > > > together.
> > > >
> > > >
> > >
> >
> ./wicket/resource/org.apache.wicket.resource.JQueryResourceReference/jquer
> > > y/jquery-1.12.4.js
> > > >
> > > >
> > >
> >
> ./wicket/resource/de.agilecoders.wicket.webjars.request.resource.WebjarsJa
> > > vaScriptResourceReference/webjars/bootstrap/3.3.7-1/js/bootstrap.js
> > > >
> > > >
> > > >> -Original 

RE: AjaxFormComponentUpdatingBehavior not triggering ListChoice model update in Firefox in Wicket 7.9.0

[Chris Colman]

Found it

It seems FireFox does have an issue with the actions that start with ..? 

The page I was going to (localhost/myapp) had a mount path at "/"

i.e.

@MountPath(value = "/", alt = "/home")

Now this mount path annotation was also in the test app that didn't exhibit the 
problem but (yes!) but the main app has a test for authenticated user with 
redirect:

// redirect to authenticate page if we don't have an authenticated user
redirectToInterceptPage(new AuthenticatePage());

The quickstart does not check for authentication so no redirect.

The problem goes away in Firefox if I change the mountpath to anything but "/" 
eg.,

@MountPath(value = "/blah", alt = "/home")

So my theory is that an action URL generated for a form in a page mounted at 
'/' is correct (./?) if the page is accessed directly without a 
redirectToInterceptPage.

but when the action URL is generated after a "continue after intercept" to a 
page that is mounted at '/' then the action URL is generated with the ..? 
prefix instead of ./?.

While Chrome can handle ..? it appears Firefox does not but works fine with ./?



> -Original Message-
> From: Chris Colman [mailto:chr...@stepaheadsoftware.com]
> Sent: Wednesday, 11 October 2017 9:29 PM
> To: users@wicket.apache.org
> Subject: RE: AjaxFormComponentUpdatingBehavior not triggering ListChoice
> model update in Firefox in Wicket 7.9.0
> 
> I found an interesting difference between the quickstart that works and
> the app that doesn't work in FF:
> 
> The action parameter of the form is generated with a .. prefix instead of
> ./
> 
> So in the app that doesn't work:
> 
> The form's action attribute is defined as:
> 
> action="..?32-1.IFormSubmitListener-form"
> 
> and in the app that does work it is defined as:
> 
> action="./?0-1.IFormSubmitListener-form"
> 
> The AJAX event handlers defined at the end of the page correspond to
> whatever was generated above.
> 
> The ..? form is generated in both Chrome and FireFox. Perhaps Firefox
> doesn't handle this ..? as well as Chrome does.
> 
> Is ..? a legal URL path?
> 
> To test this theory I could force the real app to generate a ./? URL
> instead of ..?
> 
> Any idea how I could do that?
> 
> 
> > -Original Message-
> > From: Korbinian Bachl [mailto:korbinian.ba...@whiskyworld.de]
> > Sent: Wednesday, 11 October 2017 7:12 PM
> > To: users@wicket.apache.org
> > Subject: Re: AjaxFormComponentUpdatingBehavior not triggering ListChoice
> > model update in Firefox in Wicket 7.9.0
> >
> > Is there any kind of defer or async on any of these JS script resources?
> > Maybe you want to publish the quickstart?
> >
> > - Ursprüngliche Mail -
> > > Von: "Chris Colman" 
> > > An: users@wicket.apache.org
> > > Gesendet: Mittwoch, 11. Oktober 2017 10:06:23
> > > Betreff: RE: AjaxFormComponentUpdatingBehavior not triggering
> ListChoice
> > model update in Firefox in Wicket 7.9.0
> >
> > > The cut down app that works fine in FireFox also has both jquery.js
> and
> > > bootstrap.js so this probably means that it's ok to have both of these
> > > together.
> > >
> > >
> >
> ./wicket/resource/org.apache.wicket.resource.JQueryResourceReference/jquer
> > y/jquery-1.12.4.js
> > >
> > >
> >
> ./wicket/resource/de.agilecoders.wicket.webjars.request.resource.WebjarsJa
> > vaScriptResourceReference/webjars/bootstrap/3.3.7-1/js/bootstrap.js
> > >
> > >
> > >> -Original Message-
> > >> From: Korbinian Bachl [mailto:korbinian.ba...@whiskyworld.de]
> > >> Sent: Wednesday, 11 October 2017 6:44 PM
> > >> To: users@wicket.apache.org
> > >> Subject: Re: AjaxFormComponentUpdatingBehavior not triggering
> > ListChoice
> > >> model update in Firefox in Wicket 7.9.0
> > >>
> > >> Hi Chris,
> > >>
> > >> can it be that you have 2 instances of jQuery in your page? -
> > bootstrap.js
> > >> often comes with embedded jQuery and then you would overwrite the
> > wicket
> > >> one with the bootstrap one, that will lead to problems where you dont
> > get
> > >> notfied at all. I know this from foundation / sites, where you are
> best
> > >> using a second global variable beside the one from default jQuery.
> > >>
> > >> In this part wicket is a bit of a troublemaker, you could try to
> > replace
> > >> the wicket jQuery with an empty.js resource or even pull in the
> > bootstrap
> > >> one instead (e.g.: bootstrap script file instead of wickets jquery
> only
> > >> script), so only 1 jQuery gets executed. Also the migrate you use is
> > quite
> > >> old, I would suggest 1.4.1;
> > >>
> > >> Best,
> > >>
> > >> KB
> > >>
> > >>
> > >> - Ursprüngliche Mail -
> > >> > Von: "Chris Colman" 
> > >> > An: users@wicket.apache.org
> > >> > Gesendet: Mittwoch, 11. Oktober 2017 04:39:22
> > >> > Betreff: RE: AjaxFormComponentUpdatingBehavior not triggering
> > ListChoice
> > >> model update in Firefox in Wicket 7.9.0
> > >>
> > >> > I've made some progress. I have created a cut down app 

RE: AjaxFormComponentUpdatingBehavior not triggering ListChoice model update in Firefox in Wicket 7.9.0

[Chris Colman]

I found an interesting difference between the quickstart that works and the app 
that doesn't work in FF:

The action parameter of the form is generated with a .. prefix instead of  ./

So in the app that doesn't work:

The form's action attribute is defined as:

action="..?32-1.IFormSubmitListener-form"

and in the app that does work it is defined as:

action="./?0-1.IFormSubmitListener-form"

The AJAX event handlers defined at the end of the page correspond to whatever 
was generated above.

The ..? form is generated in both Chrome and FireFox. Perhaps Firefox doesn't 
handle this ..? as well as Chrome does.

Is ..? a legal URL path?

To test this theory I could force the real app to generate a ./? URL instead of 
..? 

Any idea how I could do that?


> -Original Message-
> From: Korbinian Bachl [mailto:korbinian.ba...@whiskyworld.de]
> Sent: Wednesday, 11 October 2017 7:12 PM
> To: users@wicket.apache.org
> Subject: Re: AjaxFormComponentUpdatingBehavior not triggering ListChoice
> model update in Firefox in Wicket 7.9.0
> 
> Is there any kind of defer or async on any of these JS script resources?
> Maybe you want to publish the quickstart?
> 
> - Ursprüngliche Mail -
> > Von: "Chris Colman" 
> > An: users@wicket.apache.org
> > Gesendet: Mittwoch, 11. Oktober 2017 10:06:23
> > Betreff: RE: AjaxFormComponentUpdatingBehavior not triggering ListChoice
> model update in Firefox in Wicket 7.9.0
> 
> > The cut down app that works fine in FireFox also has both jquery.js and
> > bootstrap.js so this probably means that it's ok to have both of these
> > together.
> >
> >
> ./wicket/resource/org.apache.wicket.resource.JQueryResourceReference/jquer
> y/jquery-1.12.4.js
> >
> >
> ./wicket/resource/de.agilecoders.wicket.webjars.request.resource.WebjarsJa
> vaScriptResourceReference/webjars/bootstrap/3.3.7-1/js/bootstrap.js
> >
> >
> >> -Original Message-
> >> From: Korbinian Bachl [mailto:korbinian.ba...@whiskyworld.de]
> >> Sent: Wednesday, 11 October 2017 6:44 PM
> >> To: users@wicket.apache.org
> >> Subject: Re: AjaxFormComponentUpdatingBehavior not triggering
> ListChoice
> >> model update in Firefox in Wicket 7.9.0
> >>
> >> Hi Chris,
> >>
> >> can it be that you have 2 instances of jQuery in your page? -
> bootstrap.js
> >> often comes with embedded jQuery and then you would overwrite the
> wicket
> >> one with the bootstrap one, that will lead to problems where you dont
> get
> >> notfied at all. I know this from foundation / sites, where you are best
> >> using a second global variable beside the one from default jQuery.
> >>
> >> In this part wicket is a bit of a troublemaker, you could try to
> replace
> >> the wicket jQuery with an empty.js resource or even pull in the
> bootstrap
> >> one instead (e.g.: bootstrap script file instead of wickets jquery only
> >> script), so only 1 jQuery gets executed. Also the migrate you use is
> quite
> >> old, I would suggest 1.4.1;
> >>
> >> Best,
> >>
> >> KB
> >>
> >>
> >> - Ursprüngliche Mail -
> >> > Von: "Chris Colman" 
> >> > An: users@wicket.apache.org
> >> > Gesendet: Mittwoch, 11. Oktober 2017 04:39:22
> >> > Betreff: RE: AjaxFormComponentUpdatingBehavior not triggering
> ListChoice
> >> model update in Firefox in Wicket 7.9.0
> >>
> >> > I've made some progress. I have created a cut down app that produces
> a
> >> > similar page to the troublesome one in the large app that exhibits
> the
> >> > problem - except I can't make the cut down app exhibit the problem
> yet
> >> > ;)
> >> >
> >> > ... but I have found a suble difference between the two apps:
> >> >
> >> > It seems to be something to do with the order/inclusion of .js files
> >> > added within a HeaderResponseContainer component.
> >> >
> >> > In the working app the .js is ordered like this:
> >> > (left out unimportant tags, paths etc., for brevity)
> >> >
> >> > src="... /jquery/jquery-1.12.4.js">
> >> > src="... /wicket-event-jquery.js">
> >> > src="... /wicket-ajax-jquery.js">
> >> > 
> >> > /* >> > Wicket.Ajax.baseUrl="";
> >> > /*]]>*/
> >> > 
> >> > 
> >> > src="... /jquery-migrate-1.3.0.js">
> >> > id="bootstrap-js" src="... /
> >> > webjars/bootstrap/3.3.7-1/js/bootstrap.js">
> >> > 
> >> > /* >> >
> >> > In the app that doesn't work in FireFox the .js ordering is:
> >> >
> >> > src="... /jquery/jquery-1.12.4.js">
> >> > src="... /wicket-event-jquery.js">
> >> > src="... /js/jquery-migrate-1.3.0.js">
> >> > src="... /webjars/bootstrap/3.3.7-1/js/bootstrap.js">
> >> > src="... /prettify.js">
> >> > 
> >> > 

RE: AjaxFormComponentUpdatingBehavior not triggering ListChoice model update in Firefox in Wicket 7.9.0

[Chris Colman]

I'm trying to create a quickstart but so far it doesn't reproduce the problem 
in the main app - all day I've been pulling in aspects of the main app in an 
attempt to replicate the exact scenario.

I have now managed to get the quickstart to produce JS in the same order that 
the main app does so the ordering isn't the issue.

All the .js files in the quickstart now match the .js files in the real app - 
yet the quickstarts works fine... must be something else other than .js files 
and there ordering.

I'll keep hunting ;)

> -Original Message-
> From: Korbinian Bachl [mailto:korbinian.ba...@whiskyworld.de]
> Sent: Wednesday, 11 October 2017 7:12 PM
> To: users@wicket.apache.org
> Subject: Re: AjaxFormComponentUpdatingBehavior not triggering ListChoice
> model update in Firefox in Wicket 7.9.0
> 
> Is there any kind of defer or async on any of these JS script resources?
> Maybe you want to publish the quickstart?
> 
> - Ursprüngliche Mail -
> > Von: "Chris Colman" 
> > An: users@wicket.apache.org
> > Gesendet: Mittwoch, 11. Oktober 2017 10:06:23
> > Betreff: RE: AjaxFormComponentUpdatingBehavior not triggering ListChoice
> model update in Firefox in Wicket 7.9.0
> 
> > The cut down app that works fine in FireFox also has both jquery.js and
> > bootstrap.js so this probably means that it's ok to have both of these
> > together.
> >
> >
> ./wicket/resource/org.apache.wicket.resource.JQueryResourceReference/jquer
> y/jquery-1.12.4.js
> >
> >
> ./wicket/resource/de.agilecoders.wicket.webjars.request.resource.WebjarsJa
> vaScriptResourceReference/webjars/bootstrap/3.3.7-1/js/bootstrap.js
> >
> >
> >> -Original Message-
> >> From: Korbinian Bachl [mailto:korbinian.ba...@whiskyworld.de]
> >> Sent: Wednesday, 11 October 2017 6:44 PM
> >> To: users@wicket.apache.org
> >> Subject: Re: AjaxFormComponentUpdatingBehavior not triggering
> ListChoice
> >> model update in Firefox in Wicket 7.9.0
> >>
> >> Hi Chris,
> >>
> >> can it be that you have 2 instances of jQuery in your page? -
> bootstrap.js
> >> often comes with embedded jQuery and then you would overwrite the
> wicket
> >> one with the bootstrap one, that will lead to problems where you dont
> get
> >> notfied at all. I know this from foundation / sites, where you are best
> >> using a second global variable beside the one from default jQuery.
> >>
> >> In this part wicket is a bit of a troublemaker, you could try to
> replace
> >> the wicket jQuery with an empty.js resource or even pull in the
> bootstrap
> >> one instead (e.g.: bootstrap script file instead of wickets jquery only
> >> script), so only 1 jQuery gets executed. Also the migrate you use is
> quite
> >> old, I would suggest 1.4.1;
> >>
> >> Best,
> >>
> >> KB
> >>
> >>
> >> - Ursprüngliche Mail -
> >> > Von: "Chris Colman" 
> >> > An: users@wicket.apache.org
> >> > Gesendet: Mittwoch, 11. Oktober 2017 04:39:22
> >> > Betreff: RE: AjaxFormComponentUpdatingBehavior not triggering
> ListChoice
> >> model update in Firefox in Wicket 7.9.0
> >>
> >> > I've made some progress. I have created a cut down app that produces
> a
> >> > similar page to the troublesome one in the large app that exhibits
> the
> >> > problem - except I can't make the cut down app exhibit the problem
> yet
> >> > ;)
> >> >
> >> > ... but I have found a suble difference between the two apps:
> >> >
> >> > It seems to be something to do with the order/inclusion of .js files
> >> > added within a HeaderResponseContainer component.
> >> >
> >> > In the working app the .js is ordered like this:
> >> > (left out unimportant tags, paths etc., for brevity)
> >> >
> >> > src="... /jquery/jquery-1.12.4.js">
> >> > src="... /wicket-event-jquery.js">
> >> > src="... /wicket-ajax-jquery.js">
> >> > 
> >> > /* >> > Wicket.Ajax.baseUrl="";
> >> > /*]]>*/
> >> > 
> >> > 
> >> > src="... /jquery-migrate-1.3.0.js">
> >> > id="bootstrap-js" src="... /
> >> > webjars/bootstrap/3.3.7-1/js/bootstrap.js">
> >> > 
> >> > /* >> >
> >> > In the app that doesn't work in FireFox the .js ordering is:
> >> >
> >> > src="... /jquery/jquery-1.12.4.js">
> >> > src="... /wicket-event-jquery.js">
> >> > src="... /js/jquery-migrate-1.3.0.js">
> >> > src="... /webjars/bootstrap/3.3.7-1/js/bootstrap.js">
> >> > src="... /prettify.js">
> >> > 
> >> > 

Re: AjaxFormComponentUpdatingBehavior not triggering ListChoice model update in Firefox in Wicket 7.9.0

[Korbinian Bachl]

Is there any kind of defer or async on any of these JS script resources? 
Maybe you want to publish the quickstart?

- Ursprüngliche Mail -
> Von: "Chris Colman" 
> An: users@wicket.apache.org
> Gesendet: Mittwoch, 11. Oktober 2017 10:06:23
> Betreff: RE: AjaxFormComponentUpdatingBehavior not triggering ListChoice 
> model update in Firefox in Wicket 7.9.0

> The cut down app that works fine in FireFox also has both jquery.js and
> bootstrap.js so this probably means that it's ok to have both of these
> together.
> 
> ./wicket/resource/org.apache.wicket.resource.JQueryResourceReference/jquery/jquery-1.12.4.js
> 
> ./wicket/resource/de.agilecoders.wicket.webjars.request.resource.WebjarsJavaScriptResourceReference/webjars/bootstrap/3.3.7-1/js/bootstrap.js
> 
> 
>> -Original Message-
>> From: Korbinian Bachl [mailto:korbinian.ba...@whiskyworld.de]
>> Sent: Wednesday, 11 October 2017 6:44 PM
>> To: users@wicket.apache.org
>> Subject: Re: AjaxFormComponentUpdatingBehavior not triggering ListChoice
>> model update in Firefox in Wicket 7.9.0
>> 
>> Hi Chris,
>> 
>> can it be that you have 2 instances of jQuery in your page? - bootstrap.js
>> often comes with embedded jQuery and then you would overwrite the wicket
>> one with the bootstrap one, that will lead to problems where you dont get
>> notfied at all. I know this from foundation / sites, where you are best
>> using a second global variable beside the one from default jQuery.
>> 
>> In this part wicket is a bit of a troublemaker, you could try to replace
>> the wicket jQuery with an empty.js resource or even pull in the bootstrap
>> one instead (e.g.: bootstrap script file instead of wickets jquery only
>> script), so only 1 jQuery gets executed. Also the migrate you use is quite
>> old, I would suggest 1.4.1;
>> 
>> Best,
>> 
>> KB
>> 
>> 
>> - Ursprüngliche Mail -
>> > Von: "Chris Colman" 
>> > An: users@wicket.apache.org
>> > Gesendet: Mittwoch, 11. Oktober 2017 04:39:22
>> > Betreff: RE: AjaxFormComponentUpdatingBehavior not triggering ListChoice
>> model update in Firefox in Wicket 7.9.0
>> 
>> > I've made some progress. I have created a cut down app that produces a
>> > similar page to the troublesome one in the large app that exhibits the
>> > problem - except I can't make the cut down app exhibit the problem yet
>> > ;)
>> >
>> > ... but I have found a suble difference between the two apps:
>> >
>> > It seems to be something to do with the order/inclusion of .js files
>> > added within a HeaderResponseContainer component.
>> >
>> > In the working app the .js is ordered like this:
>> > (left out unimportant tags, paths etc., for brevity)
>> >
>> > src="... /jquery/jquery-1.12.4.js">
>> > src="... /wicket-event-jquery.js">
>> > src="... /wicket-ajax-jquery.js">
>> > 
>> > /*> > Wicket.Ajax.baseUrl="";
>> > /*]]>*/
>> > 
>> > 
>> > src="... /jquery-migrate-1.3.0.js">
>> > id="bootstrap-js" src="... /
>> > webjars/bootstrap/3.3.7-1/js/bootstrap.js">
>> > 
>> > /*> >
>> > In the app that doesn't work in FireFox the .js ordering is:
>> >
>> > src="... /jquery/jquery-1.12.4.js">
>> > src="... /wicket-event-jquery.js">
>> > src="... /js/jquery-migrate-1.3.0.js">
>> > src="... /webjars/bootstrap/3.3.7-1/js/bootstrap.js">
>> > src="... /prettify.js">
>> > 
>> > 

RE: AjaxFormComponentUpdatingBehavior not triggering ListChoice model update in Firefox in Wicket 7.9.0

[Chris Colman]

The cut down app that works fine in FireFox also has both jquery.js and 
bootstrap.js so this probably means that it's ok to have both of these together.

./wicket/resource/org.apache.wicket.resource.JQueryResourceReference/jquery/jquery-1.12.4.js

./wicket/resource/de.agilecoders.wicket.webjars.request.resource.WebjarsJavaScriptResourceReference/webjars/bootstrap/3.3.7-1/js/bootstrap.js


> -Original Message-
> From: Korbinian Bachl [mailto:korbinian.ba...@whiskyworld.de]
> Sent: Wednesday, 11 October 2017 6:44 PM
> To: users@wicket.apache.org
> Subject: Re: AjaxFormComponentUpdatingBehavior not triggering ListChoice
> model update in Firefox in Wicket 7.9.0
> 
> Hi Chris,
> 
> can it be that you have 2 instances of jQuery in your page? - bootstrap.js
> often comes with embedded jQuery and then you would overwrite the wicket
> one with the bootstrap one, that will lead to problems where you dont get
> notfied at all. I know this from foundation / sites, where you are best
> using a second global variable beside the one from default jQuery.
> 
> In this part wicket is a bit of a troublemaker, you could try to replace
> the wicket jQuery with an empty.js resource or even pull in the bootstrap
> one instead (e.g.: bootstrap script file instead of wickets jquery only
> script), so only 1 jQuery gets executed. Also the migrate you use is quite
> old, I would suggest 1.4.1;
> 
> Best,
> 
> KB
> 
> 
> - Ursprüngliche Mail -
> > Von: "Chris Colman" 
> > An: users@wicket.apache.org
> > Gesendet: Mittwoch, 11. Oktober 2017 04:39:22
> > Betreff: RE: AjaxFormComponentUpdatingBehavior not triggering ListChoice
> model update in Firefox in Wicket 7.9.0
> 
> > I've made some progress. I have created a cut down app that produces a
> > similar page to the troublesome one in the large app that exhibits the
> > problem - except I can't make the cut down app exhibit the problem yet
> > ;)
> >
> > ... but I have found a suble difference between the two apps:
> >
> > It seems to be something to do with the order/inclusion of .js files
> > added within a HeaderResponseContainer component.
> >
> > In the working app the .js is ordered like this:
> > (left out unimportant tags, paths etc., for brevity)
> >
> > src="... /jquery/jquery-1.12.4.js">
> > src="... /wicket-event-jquery.js">
> > src="... /wicket-ajax-jquery.js">
> > 
> > /* > Wicket.Ajax.baseUrl="";
> > /*]]>*/
> > 
> > 
> > src="... /jquery-migrate-1.3.0.js">
> > id="bootstrap-js" src="... /
> > webjars/bootstrap/3.3.7-1/js/bootstrap.js">
> > 
> > /* >
> > In the app that doesn't work in FireFox the .js ordering is:
> >
> > src="... /jquery/jquery-1.12.4.js">
> > src="... /wicket-event-jquery.js">
> > src="... /js/jquery-migrate-1.3.0.js">
> > src="... /webjars/bootstrap/3.3.7-1/js/bootstrap.js">
> > src="... /prettify.js">
> > 
> > 

RE: AjaxFormComponentUpdatingBehavior not triggering ListChoice model update in Firefox in Wicket 7.9.0

[Chris Colman]

Thanks Korginian - I'll check out that theory.

All the JS included are done automatically by a combo of Wicket itself and the 
Wicket-Bootstrap project which I'm using in this app.

Is there an easy way to tell which component is contributing which .js to the 
"header" (which is actually in the footer as I'm using a 
HeaderResponseContaine)?

> -Original Message-
> From: Korbinian Bachl [mailto:korbinian.ba...@whiskyworld.de]
> Sent: Wednesday, 11 October 2017 6:44 PM
> To: users@wicket.apache.org
> Subject: Re: AjaxFormComponentUpdatingBehavior not triggering ListChoice
> model update in Firefox in Wicket 7.9.0
> 
> Hi Chris,
> 
> can it be that you have 2 instances of jQuery in your page? - bootstrap.js
> often comes with embedded jQuery and then you would overwrite the wicket
> one with the bootstrap one, that will lead to problems where you dont get
> notfied at all. I know this from foundation / sites, where you are best
> using a second global variable beside the one from default jQuery.
> 
> In this part wicket is a bit of a troublemaker, you could try to replace
> the wicket jQuery with an empty.js resource or even pull in the bootstrap
> one instead (e.g.: bootstrap script file instead of wickets jquery only
> script), so only 1 jQuery gets executed. Also the migrate you use is quite
> old, I would suggest 1.4.1;
> 
> Best,
> 
> KB
> 
> 
> - Ursprüngliche Mail -
> > Von: "Chris Colman" 
> > An: users@wicket.apache.org
> > Gesendet: Mittwoch, 11. Oktober 2017 04:39:22
> > Betreff: RE: AjaxFormComponentUpdatingBehavior not triggering ListChoice
> model update in Firefox in Wicket 7.9.0
> 
> > I've made some progress. I have created a cut down app that produces a
> > similar page to the troublesome one in the large app that exhibits the
> > problem - except I can't make the cut down app exhibit the problem yet
> > ;)
> >
> > ... but I have found a suble difference between the two apps:
> >
> > It seems to be something to do with the order/inclusion of .js files
> > added within a HeaderResponseContainer component.
> >
> > In the working app the .js is ordered like this:
> > (left out unimportant tags, paths etc., for brevity)
> >
> > src="... /jquery/jquery-1.12.4.js">
> > src="... /wicket-event-jquery.js">
> > src="... /wicket-ajax-jquery.js">
> > 
> > /* > Wicket.Ajax.baseUrl="";
> > /*]]>*/
> > 
> > 
> > src="... /jquery-migrate-1.3.0.js">
> > id="bootstrap-js" src="... /
> > webjars/bootstrap/3.3.7-1/js/bootstrap.js">
> > 
> > /* >
> > In the app that doesn't work in FireFox the .js ordering is:
> >
> > src="... /jquery/jquery-1.12.4.js">
> > src="... /wicket-event-jquery.js">
> > src="... /js/jquery-migrate-1.3.0.js">
> > src="... /webjars/bootstrap/3.3.7-1/js/bootstrap.js">
> > src="... /prettify.js">
> > 
> > 

Re: AjaxFormComponentUpdatingBehavior not triggering ListChoice model update in Firefox in Wicket 7.9.0

[Korbinian Bachl]

Hi Chris,

can it be that you have 2 instances of jQuery in your page? - bootstrap.js 
often comes with embedded jQuery and then you would overwrite the wicket one 
with the bootstrap one, that will lead to problems where you dont get notfied 
at all. I know this from foundation / sites, where you are best using a second 
global variable beside the one from default jQuery.

In this part wicket is a bit of a troublemaker, you could try to replace the 
wicket jQuery with an empty.js resource or even pull in the bootstrap one 
instead (e.g.: bootstrap script file instead of wickets jquery only script), so 
only 1 jQuery gets executed. Also the migrate you use is quite old, I would 
suggest 1.4.1;

Best,

KB


- Ursprüngliche Mail -
> Von: "Chris Colman" 
> An: users@wicket.apache.org
> Gesendet: Mittwoch, 11. Oktober 2017 04:39:22
> Betreff: RE: AjaxFormComponentUpdatingBehavior not triggering ListChoice 
> model update in Firefox in Wicket 7.9.0

> I've made some progress. I have created a cut down app that produces a
> similar page to the troublesome one in the large app that exhibits the
> problem - except I can't make the cut down app exhibit the problem yet
> ;)
> 
> ... but I have found a suble difference between the two apps:
> 
> It seems to be something to do with the order/inclusion of .js files
> added within a HeaderResponseContainer component.
> 
> In the working app the .js is ordered like this:
> (left out unimportant tags, paths etc., for brevity)
> 
> src="... /jquery/jquery-1.12.4.js">
> src="... /wicket-event-jquery.js">
> src="... /wicket-ajax-jquery.js">
> 
> /* Wicket.Ajax.baseUrl="";
> /*]]>*/
> 
> 
> src="... /jquery-migrate-1.3.0.js">
> id="bootstrap-js" src="... /
> webjars/bootstrap/3.3.7-1/js/bootstrap.js">
> 
> /* 
> In the app that doesn't work in FireFox the .js ordering is:
> 
> src="... /jquery/jquery-1.12.4.js">
> src="... /wicket-event-jquery.js">
> src="... /js/jquery-migrate-1.3.0.js">
> src="... /webjars/bootstrap/3.3.7-1/js/bootstrap.js">
> src="... /prettify.js">
> 
> 

RE: AjaxFormComponentUpdatingBehavior not triggering ListChoice model update in Firefox in Wicket 7.9.0

[Chris Colman]

I've made some progress. I have created a cut down app that produces a
similar page to the troublesome one in the large app that exhibits the
problem - except I can't make the cut down app exhibit the problem yet
;)

... but I have found a suble difference between the two apps:

It seems to be something to do with the order/inclusion of .js files
added within a HeaderResponseContainer component.

In the working app the .js is ordered like this:
(left out unimportant tags, paths etc., for brevity)

src="... /jquery/jquery-1.12.4.js">
src="... /wicket-event-jquery.js">
src="... /wicket-ajax-jquery.js">

/**/


src="... /jquery-migrate-1.3.0.js">
id="bootstrap-js" src="... /
webjars/bootstrap/3.3.7-1/js/bootstrap.js">

/*
src="... /wicket-event-jquery.js">
src="... /js/jquery-migrate-1.3.0.js">
src="... /webjars/bootstrap/3.3.7-1/js/bootstrap.js">
src="... /prettify.js">

RE: AjaxFormComponentUpdatingBehavior not triggering ListChoice model update in Firefox in Wicket 7.9.0

[Chris Colman]

I disabled all plugins and add-ons but it still happens.

I'll try to create a quickstart that reproduces the problem.

> -Original Message-
> From: Andrea Del Bene [mailto:an.delb...@gmail.com]
> Sent: Saturday, 7 October 2017 12:33 AM
> To: users@wicket.apache.org
> Subject: Re: AjaxFormComponentUpdatingBehavior not triggering
ListChoice
> model update in Firefox in Wicket 7.9.0
> 
> Hi,
> 
> I've tried your code but everything works fine. Maybe your FF has an
add-
> on
> that causes the problem ?
> 
> On Fri, Oct 6, 2017 at 1:21 PM, Chris Colman
> 
> wrote:
> 
> > I also tried it without the leading 'on' in 'onchange'
> >
> > > -Original Message-
> > > From: Chris Colman [mailto:chr...@stepaheadsoftware.com]
> > > Sent: Friday, 6 October 2017 10:12 PM
> > > To: users@wicket.apache.org
> > > Subject: AjaxFormComponentUpdatingBehavior not triggering
ListChoice
> > model
> > > update in Firefox in Wicket 7.9.0
> > >
> > > I have a ListChoice with a ProperyModel and I have added a
> > > AjaxFormComponentUpdatingBehavior to cause the model object to be
> > > updated 'live' (i.e. whenever the selection is changed rather than
> > > waiting for form submit) via:
> > >
> > >
> > >   myListChoice.add(new
> > > AjaxFormComponentUpdatingBehavior("onchange") {
> > >   @Override
> > >   protected void onUpdate(AjaxRequestTarget target)
> > >   {
> > >   logger.info("Item changed");
> > >   }
> > >   });
> > >
> > > In all browsers the "Item changed" log entry occurs every time the
> > > selection in the ListChoice is changed.
> > >
> > > However in Firefox the model object is not updated to the latest
> > > selection while in Chrome and Edge this works perfectly.
> > >
> > > Am I doing anything wrong or is there something simple I can do to
get
> > > it working in FireFox?
> > >
> > >
-
> > > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> > > For additional commands, e-mail: users-h...@wicket.apache.org
> >
> >
> >
-
> > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> > For additional commands, e-mail: users-h...@wicket.apache.org
> >
> >

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

RE: AjaxFormComponentUpdatingBehavior not triggering ListChoice model update in Firefox in Wicket 7.9.0

[Chris Colman]

I'm running Wicket with wicket-bootstrap but I wouldn't think that would
cause any issues.

> -Original Message-
> From: Andrea Del Bene [mailto:an.delb...@gmail.com]
> Sent: Saturday, 7 October 2017 12:33 AM
> To: users@wicket.apache.org
> Subject: Re: AjaxFormComponentUpdatingBehavior not triggering
ListChoice
> model update in Firefox in Wicket 7.9.0
> 
> Hi,
> 
> I've tried your code but everything works fine. Maybe your FF has an
add-
> on
> that causes the problem ?
> 
> On Fri, Oct 6, 2017 at 1:21 PM, Chris Colman
> 
> wrote:
> 
> > I also tried it without the leading 'on' in 'onchange'
> >
> > > -Original Message-
> > > From: Chris Colman [mailto:chr...@stepaheadsoftware.com]
> > > Sent: Friday, 6 October 2017 10:12 PM
> > > To: users@wicket.apache.org
> > > Subject: AjaxFormComponentUpdatingBehavior not triggering
ListChoice
> > model
> > > update in Firefox in Wicket 7.9.0
> > >
> > > I have a ListChoice with a ProperyModel and I have added a
> > > AjaxFormComponentUpdatingBehavior to cause the model object to be
> > > updated 'live' (i.e. whenever the selection is changed rather than
> > > waiting for form submit) via:
> > >
> > >
> > >   myListChoice.add(new
> > > AjaxFormComponentUpdatingBehavior("onchange") {
> > >   @Override
> > >   protected void onUpdate(AjaxRequestTarget target)
> > >   {
> > >   logger.info("Item changed");
> > >   }
> > >   });
> > >
> > > In all browsers the "Item changed" log entry occurs every time the
> > > selection in the ListChoice is changed.
> > >
> > > However in Firefox the model object is not updated to the latest
> > > selection while in Chrome and Edge this works perfectly.
> > >
> > > Am I doing anything wrong or is there something simple I can do to
get
> > > it working in FireFox?
> > >
> > >
-
> > > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> > > For additional commands, e-mail: users-h...@wicket.apache.org
> >
> >
> >
-
> > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> > For additional commands, e-mail: users-h...@wicket.apache.org
> >
> >

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Re: AjaxFormComponentUpdatingBehavior not triggering ListChoice model update in Firefox in Wicket 7.9.0

[Andrea Del Bene]

Hi,

I've tried your code but everything works fine. Maybe your FF has an add-on
that causes the problem ?

On Fri, Oct 6, 2017 at 1:21 PM, Chris Colman 
wrote:

> I also tried it without the leading 'on' in 'onchange'
>
> > -Original Message-
> > From: Chris Colman [mailto:chr...@stepaheadsoftware.com]
> > Sent: Friday, 6 October 2017 10:12 PM
> > To: users@wicket.apache.org
> > Subject: AjaxFormComponentUpdatingBehavior not triggering ListChoice
> model
> > update in Firefox in Wicket 7.9.0
> >
> > I have a ListChoice with a ProperyModel and I have added a
> > AjaxFormComponentUpdatingBehavior to cause the model object to be
> > updated 'live' (i.e. whenever the selection is changed rather than
> > waiting for form submit) via:
> >
> >
> >   myListChoice.add(new
> > AjaxFormComponentUpdatingBehavior("onchange") {
> >   @Override
> >   protected void onUpdate(AjaxRequestTarget target)
> >   {
> >   logger.info("Item changed");
> >   }
> >   });
> >
> > In all browsers the "Item changed" log entry occurs every time the
> > selection in the ListChoice is changed.
> >
> > However in Firefox the model object is not updated to the latest
> > selection while in Chrome and Edge this works perfectly.
> >
> > Am I doing anything wrong or is there something simple I can do to get
> > it working in FireFox?
> >
> > -
> > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> > For additional commands, e-mail: users-h...@wicket.apache.org
>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> For additional commands, e-mail: users-h...@wicket.apache.org
>
>

RE: AjaxFormComponentUpdatingBehavior not triggering ListChoice model update in Firefox in Wicket 7.9.0

[Chris Colman]

I also tried it without the leading 'on' in 'onchange'

> -Original Message-
> From: Chris Colman [mailto:chr...@stepaheadsoftware.com]
> Sent: Friday, 6 October 2017 10:12 PM
> To: users@wicket.apache.org
> Subject: AjaxFormComponentUpdatingBehavior not triggering ListChoice
model
> update in Firefox in Wicket 7.9.0
> 
> I have a ListChoice with a ProperyModel and I have added a
> AjaxFormComponentUpdatingBehavior to cause the model object to be
> updated 'live' (i.e. whenever the selection is changed rather than
> waiting for form submit) via:
> 
> 
>   myListChoice.add(new
> AjaxFormComponentUpdatingBehavior("onchange") {
>   @Override
>   protected void onUpdate(AjaxRequestTarget target)
>   {
>   logger.info("Item changed");
>   }
>   });
> 
> In all browsers the "Item changed" log entry occurs every time the
> selection in the ListChoice is changed.
> 
> However in Firefox the model object is not updated to the latest
> selection while in Chrome and Edge this works perfectly.
> 
> Am I doing anything wrong or is there something simple I can do to get
> it working in FireFox?
> 
> -
> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> For additional commands, e-mail: users-h...@wicket.apache.org


-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org