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 <[email protected]> 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: [email protected]
> 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: [email protected]
> For additional commands, e-mail: [email protected]
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to