[Tickets #11099] Re: Incorrect order of javascript

[bugs at horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/11099
------------------------------------------------------------------------------
  Ticket             | 11099
  Updated By         | Michael Slusarz <slusarz at horde.org>
  Summary            | Incorrect order of javascript
  Queue              | Horde Framework Packages
  Version            | Git develop
  Type               | Bug
  State              | Feedback
  Priority           | 2. Medium
  Milestone          |
  Patch              |
  Owners             | Michael Slusarz
------------------------------------------------------------------------------


Michael Slusarz <slusarz at horde.org> (2012-03-23 14:53) wrote:

> If output has been started already, any inlineScripts (and thus any  
> inlinJsVars too) are printed immediately if onload has been specified.
> This happens in Trean for example, if you need a real-life example.

And that's the expected behavior, right?  It is wrapped in a  
dom:loaded event, and is not attempted to be inserted into the Horde  
object until the page is loaded, since there is a chance that the  
Horde object won't be loaded until later in the page?

Unfortunately, I don't have trean configured on my server to test.