[
https://issues.apache.org/jira/browse/TRINIDAD-1777?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Scott O'Bryan updated TRINIDAD-1777:
------------------------------------
Status: Open (was: Patch Available)
> new JS execution order if in head
> ---------------------------------
>
> Key: TRINIDAD-1777
> URL: https://issues.apache.org/jira/browse/TRINIDAD-1777
> Project: MyFaces Trinidad
> Issue Type: Bug
> Components: Components
> Affects Versions: 1.2.13-core
> Environment: RH Linux, JBOSS 4.2
> Reporter: Wolfgang Chico Toepfer
> Priority: Minor
> Attachments: Seamidad1_2_13_Bugs.zip
>
>
> Recently we tried to update from 1.2.9 to 1.2.13 -btw we were testing the
> releases in between and they seemed ok- and now it looks as if we were
> stuck with this version. Because of the following effect, our application
> did not work anymore as expected:
> Trinidad's JS Object TrRequestQueue is not anymore found when we try to
> address it in our Java Script i.e. it seems there is a new execution order
> in command; the consequence, for instance, is that when we try to override
> the alerError function to redirect the error to something else than the
> not-so-nice JS Trinidad popup we cannot do this anymore; in our template
> page we set
> ...
> <trh:head>
> <title>..</title>
> <meta
> http-equiv="Content-Type"
> content="text/html; charset=UTF-8" />
> ...
> <script
> src="#{request.contextPath}/js/ourJavaScript.js"
> type="text/javascript" />
> ...
> </trh:head>
> ...
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
