You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Andreas Andreou (JIRA)" <de...@tapestry.apache.org> on 2008/01/22 18:08:34 UTC
[jira] Updated: (TAPESTRY-1219) The order of loading bodyscripts
and initializationscripts is non deterministic
[ https://issues.apache.org/jira/browse/TAPESTRY-1219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andreas Andreou updated TAPESTRY-1219:
--------------------------------------
Fix Version/s: (was: 4.1.4)
4.1.5
> The order of loading bodyscripts and initializationscripts is non deterministic
> -------------------------------------------------------------------------------
>
> Key: TAPESTRY-1219
> URL: https://issues.apache.org/jira/browse/TAPESTRY-1219
> Project: Tapestry
> Issue Type: Bug
> Components: XHR/dhtml/Ajax
> Affects Versions: 4.1.1
> Environment: FF 2.0
> Reporter: Andreas Andreou
> Assignee: Andreas Andreou
> Fix For: 4.1.5
>
>
> A comment in core.js reads 'load body scripts before initialization'...
> Due to the way loadScriptContent has to be implemented (to circumvent IE issues) this doesn't always hold true.
> So, a call to taperstry.widget.synchronizeWidgetState (in an initialization script) can sometimes get executed BEFORE a
> dojo.require('tapestry.widget.Widget') (typically in body scripts) resulting in
> 'taperstry.widget.synchronizeWidgetState not a function' javascript errors.
> Perhaps somehow block until all body scripts get processed?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org