You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@wicket.apache.org by Antoine Angenieux <aa...@clinigrid.com> on 2010/11/29 15:42:52 UTC

Wicket 1.4.14 > Bug with panels updated by Ajax rendering a CSS

Hi all,

I have just upgraded my dev environment from Wicket 1.4.13 to 1.4.14 
this morning and discovered a bug related to CSS.

On a page, I have a panel containing a listview, itself populated with 
panels that have in their constructor:
add(CSSPackageResource.getHeaderContribution(CSS));

When browsing to this page, the listview is initially empty. When the 
panel is updated by an Ajax Link making the listview model list not 
empty, the list view contents are rendered, but the CSS is not (and the 
reference to the css script does not appear in the Wicket Ajax Debug 
Window), and thus the presentation is all messed up.

I just downgraded back to Wicket 1.4.13, and all is fine.

I don't have time to prepare a Quickstart yet, but if anyone who has 
been fixing bugs on Wicket 1.4.14 has a brilliant intuition on what can 
cause this regression, it would be great ;)

Otherwise, I'll try to find sometime later this week to file a JIRA 
issue with a Quickstart.

Cheers,

Antoine.


-- 
Antoine Angénieux
Associé

Clinigrid
5, avenue Mozart
75016 Paris, France
+336 60 21 09 18
aangenieux@clinigrid.com


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


Re: Wicket 1.4.14 > Bug with panels updated by Ajax rendering a CSS

Posted by Ernesto Reinaldo Barreiro <re...@gmail.com>.
http://apache-wicket.1842946.n4.nabble.com/Re-svn-commit-r1031432-wicket-branches-wicket-1-4-x-wicket-src-main-java-org-apache-wicket-ajax-Ajaxa-tt3067178.html

Ernesto

On Wed, Dec 1, 2010 at 3:01 PM, Brad Grier <br...@salusnovus.com> wrote:
> Let me know how it goes. I can't help but think this bug is related to the
> problem I'm seeing.
>
> -----Original Message----- From: Antoine Angénieux
> Sent: Tuesday, November 30, 2010 7:05 AM
> To: users@wicket.apache.org
> Subject: Re: Wicket 1.4.14 > Bug with panels updated by Ajax rendering a CSS
>
> Nobody has any idea on the subject ?
>
> OK, I'll come up with a quickstart this WE !
>
> Cheers,
>
> Antoine.
>
> Le 29/11/2010 15:42, Antoine Angenieux a écrit :
>>
>> Hi all,
>>
>> I have just upgraded my dev environment from Wicket 1.4.13 to 1.4.14
>> this morning and discovered a bug related to CSS.
>>
>> On a page, I have a panel containing a listview, itself populated with
>> panels that have in their constructor:
>> add(CSSPackageResource.getHeaderContribution(CSS));
>>
>> When browsing to this page, the listview is initially empty. When the
>> panel is updated by an Ajax Link making the listview model list not
>> empty, the list view contents are rendered, but the CSS is not (and the
>> reference to the css script does not appear in the Wicket Ajax Debug
>> Window), and thus the presentation is all messed up.
>>
>> I just downgraded back to Wicket 1.4.13, and all is fine.
>>
>> I don't have time to prepare a Quickstart yet, but if anyone who has
>> been fixing bugs on Wicket 1.4.14 has a brilliant intuition on what can
>> cause this regression, it would be great ;)
>>
>> Otherwise, I'll try to find sometime later this week to file a JIRA
>> issue with a Quickstart.
>>
>> Cheers,
>>
>> Antoine.
>>
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>

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


Re: Wicket 1.4.14 > Bug with panels updated by Ajax rendering a CSS

Posted by Antoine Angénieux <aa...@yahoo.fr>.
Hi Brad,

I think Johan Compagner has found the issue, see the thread in dev list 
started a few hours ago: svn commit: r1031432 - 
/wicket/branches/wicket-1.4.x/wicket/src/main/java/org/apache/wicket/ajax/AjaxRequestTarget.java

It looks like this is all related to that commit.

I'll be waiting for Wicket 1.4.15 before upgrading my current 
applications from Wicket 1.4.13.

Cheers,

Antoine.

Le 01/12/2010 15:01, Brad Grier a écrit :
> Let me know how it goes. I can't help but think this bug is related to
> the problem I'm seeing.
>
> -----Original Message----- From: Antoine Angénieux
> Sent: Tuesday, November 30, 2010 7:05 AM
> To: users@wicket.apache.org
> Subject: Re: Wicket 1.4.14 > Bug with panels updated by Ajax rendering a
> CSS
>
> Nobody has any idea on the subject ?
>
> OK, I'll come up with a quickstart this WE !
>
> Cheers,
>
> Antoine.
>
> Le 29/11/2010 15:42, Antoine Angenieux a écrit :
>> Hi all,
>>
>> I have just upgraded my dev environment from Wicket 1.4.13 to 1.4.14
>> this morning and discovered a bug related to CSS.
>>
>> On a page, I have a panel containing a listview, itself populated with
>> panels that have in their constructor:
>> add(CSSPackageResource.getHeaderContribution(CSS));
>>
>> When browsing to this page, the listview is initially empty. When the
>> panel is updated by an Ajax Link making the listview model list not
>> empty, the list view contents are rendered, but the CSS is not (and the
>> reference to the css script does not appear in the Wicket Ajax Debug
>> Window), and thus the presentation is all messed up.
>>
>> I just downgraded back to Wicket 1.4.13, and all is fine.
>>
>> I don't have time to prepare a Quickstart yet, but if anyone who has
>> been fixing bugs on Wicket 1.4.14 has a brilliant intuition on what can
>> cause this regression, it would be great ;)
>>
>> Otherwise, I'll try to find sometime later this week to file a JIRA
>> issue with a Quickstart.
>>
>> Cheers,
>>
>> Antoine.
>>
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
>
> -----
> Aucun virus trouvé dans ce message.
> Analyse effectuée par AVG - www.avg.fr
> Version: 10.0.1170 / Base de données virale: 426/3290 - Date: 30/11/2010
>


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


Re: Wicket 1.4.14 > Bug with panels updated by Ajax rendering a CSS

Posted by Brad Grier <br...@salusnovus.com>.
Let me know how it goes. I can't help but think this bug is related to the 
problem I'm seeing.

-----Original Message----- 
From: Antoine Angénieux
Sent: Tuesday, November 30, 2010 7:05 AM
To: users@wicket.apache.org
Subject: Re: Wicket 1.4.14 > Bug with panels updated by Ajax rendering a CSS

Nobody has any idea on the subject ?

OK, I'll come up with a quickstart this WE !

Cheers,

Antoine.

Le 29/11/2010 15:42, Antoine Angenieux a écrit :
> Hi all,
>
> I have just upgraded my dev environment from Wicket 1.4.13 to 1.4.14
> this morning and discovered a bug related to CSS.
>
> On a page, I have a panel containing a listview, itself populated with
> panels that have in their constructor:
> add(CSSPackageResource.getHeaderContribution(CSS));
>
> When browsing to this page, the listview is initially empty. When the
> panel is updated by an Ajax Link making the listview model list not
> empty, the list view contents are rendered, but the CSS is not (and the
> reference to the css script does not appear in the Wicket Ajax Debug
> Window), and thus the presentation is all messed up.
>
> I just downgraded back to Wicket 1.4.13, and all is fine.
>
> I don't have time to prepare a Quickstart yet, but if anyone who has
> been fixing bugs on Wicket 1.4.14 has a brilliant intuition on what can
> cause this regression, it would be great ;)
>
> Otherwise, I'll try to find sometime later this week to file a JIRA
> issue with a Quickstart.
>
> Cheers,
>
> Antoine.
>
>


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


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


Re: Wicket 1.4.14 > Bug with panels updated by Ajax rendering a CSS

Posted by Antoine Angénieux <aa...@yahoo.fr>.
Nobody has any idea on the subject ?

OK, I'll come up with a quickstart this WE !

Cheers,

Antoine.

Le 29/11/2010 15:42, Antoine Angenieux a écrit :
> Hi all,
>
> I have just upgraded my dev environment from Wicket 1.4.13 to 1.4.14
> this morning and discovered a bug related to CSS.
>
> On a page, I have a panel containing a listview, itself populated with
> panels that have in their constructor:
> add(CSSPackageResource.getHeaderContribution(CSS));
>
> When browsing to this page, the listview is initially empty. When the
> panel is updated by an Ajax Link making the listview model list not
> empty, the list view contents are rendered, but the CSS is not (and the
> reference to the css script does not appear in the Wicket Ajax Debug
> Window), and thus the presentation is all messed up.
>
> I just downgraded back to Wicket 1.4.13, and all is fine.
>
> I don't have time to prepare a Quickstart yet, but if anyone who has
> been fixing bugs on Wicket 1.4.14 has a brilliant intuition on what can
> cause this regression, it would be great ;)
>
> Otherwise, I'll try to find sometime later this week to file a JIRA
> issue with a Quickstart.
>
> Cheers,
>
> Antoine.
>
>


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


Re: Wicket 1.4.14 > Bug with panels updated by Ajax rendering a CSS

Posted by Brad Grier <br...@salusnovus.com>.
Since upgrading the tabs from wiQuery 1.02 no longer work in my application. 
Could be related as the CSS isn't being picked up at all. These are tabs on 
panels displayed via ajax.

-----Original Message----- 
From: Antoine Angenieux
Sent: Monday, November 29, 2010 8:42 AM
To: users@wicket.apache.org
Subject: Wicket 1.4.14 > Bug with panels updated by Ajax rendering a CSS

Hi all,

I have just upgraded my dev environment from Wicket 1.4.13 to 1.4.14
this morning and discovered a bug related to CSS.

On a page, I have a panel containing a listview, itself populated with
panels that have in their constructor:
add(CSSPackageResource.getHeaderContribution(CSS));

When browsing to this page, the listview is initially empty. When the
panel is updated by an Ajax Link making the listview model list not
empty, the list view contents are rendered, but the CSS is not (and the
reference to the css script does not appear in the Wicket Ajax Debug
Window), and thus the presentation is all messed up.

I just downgraded back to Wicket 1.4.13, and all is fine.

I don't have time to prepare a Quickstart yet, but if anyone who has
been fixing bugs on Wicket 1.4.14 has a brilliant intuition on what can
cause this regression, it would be great ;)

Otherwise, I'll try to find sometime later this week to file a JIRA
issue with a Quickstart.

Cheers,

Antoine.


-- 
Antoine Angénieux
Associé

Clinigrid
5, avenue Mozart
75016 Paris, France
+336 60 21 09 18
aangenieux@clinigrid.com


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


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