[
https://issues.apache.org/jira/browse/WICKET-3927?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor Vaynberg updated WICKET-3927:
----------------------------------
Fix Version/s: 1.6.0
Summary: Use a resource loading lib to setup order for processing
ajax response fragments (was: Wait for CSS head contributions to be rendered
before processing other contributions)
we will get to this when we rewrite ajax for 1.6.
essentially what we can do is use a loader lib and do this:
load all css resources in parallel
wait for all of them to finish
execute any inline css
load all javascript resources in parallel
wait for all of them to finish
execute any inline js
> 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
