You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tapestry.apache.org by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org> on 2010/05/07 19:31:48 UTC

[jira] Updated: (TAP5-1137) Dynamically adding JavaScript libraries to a page via a partial page update does not seem to work consistently in Safari and Chromie

     [ https://issues.apache.org/jira/browse/TAP5-1137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Howard M. Lewis Ship updated TAP5-1137:
---------------------------------------

        Summary: Dynamically adding JavaScript libraries to a page via a partial page update does not seem to work consistently in Safari and Chromie  (was: Dynamically adding JavaScript libraries to a page via a partial page update does not seem to work properly in Safari and Chromie)
    Description: When scripts have dependencies on each other, it appears they can be loaded and executed out-of-order, causing runtime exceptions in the browser.

Ideally, dependencies wouldn't be resolved until a DOM Loaded event handler, but that's not always the case (tapx-datefield uses a library that breaks this rule).

The approach I'm working with is to load each added script sequentially, rather than creating a batch of new <script> elements and waiting for them all to complete (in indeterminate order).

> Dynamically adding JavaScript libraries to a page via a partial page update does not seem to work consistently in Safari and Chromie
> ------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: TAP5-1137
>                 URL: https://issues.apache.org/jira/browse/TAP5-1137
>             Project: Tapestry 5
>          Issue Type: Bug
>          Components: tapestry-core
>    Affects Versions: 5.2.0
>            Reporter: Howard M. Lewis Ship
>            Assignee: Howard M. Lewis Ship
>            Priority: Blocker
>
> When scripts have dependencies on each other, it appears they can be loaded and executed out-of-order, causing runtime exceptions in the browser.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.