[ 
https://issues.apache.org/jira/browse/WICKET-3927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13119148#comment-13119148
 ] 

Martin Grigorov commented on WICKET-3927:
-----------------------------------------

Last week I added some improvements related to this ticket in 1.5.x. Now the 
header contributions are executed one by one waiting for external scripts and 
CSSs to be loaded before proceeding.
I think they should be good enough for the requirements in this ticket. Please 
give them a try.
                
> Use a resource loading lib to setup order for processing ajax response 
> fragments
> --------------------------------------------------------------------------------
>
>                 Key: WICKET-3927
>                 URL: https://issues.apache.org/jira/browse/WICKET-3927
>             Project: Wicket
>          Issue Type: Bug
>          Components: wicket
>    Affects Versions: 1.4.17, 1.5-RC5.1
>         Environment: I tested Firefox 4, IE 7, 8, 9 and Chromium 12.0.742.112
>            Reporter: Jannis Bloemendal
>             Fix For: 1.6.0
>
>         Attachments: WICKET-3927-quickstart.tar.gz, WICKET-3927.patch, 
> WICKET-3927_2.patch
>
>
> When css head contributions are added by an ajax response, executed / 
> contributed javascript  can not rely on the css to be rendered. This can for 
> example be a problem for a javascript layout manager which gets triggered 
> with the ajax response. 
> It is more a short-come of current browsers, but can be worked around for 
> example by the method described in the blog post:
> "CSSP: Loading CSS with Javascript - and getting an onload callback."
> http://otaqui.com/blog/890/cssp-loading-css-with-javascript-and-getting-an-onload-callback/

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to