You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Jesse Kuhnert (JIRA)" <ta...@jakarta.apache.org> on 2007/02/15 03:05:05 UTC

[jira] Commented: (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:comment-tabpanel#action_12473287 ] 

Jesse Kuhnert commented on TAPESTRY-1219:
-----------------------------------------

Dunno ....Do you have an example of where this has happened? Ie is it worth the effort?

> 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
>            Priority: Critical
>             Fix For: 4.1.2
>
>
> 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