[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         | Jan Schneider <jan at horde.org>
  Summary            | Incorrect order of javascript
  Queue              | Horde Framework Packages
  Version            | Git develop
  Type               | Bug
-State              | Feedback
+State              | Resolved
  Priority           | 2. Medium
  Milestone          |
  Patch              |
  Owners             | Michael Slusarz
------------------------------------------------------------------------------


Jan Schneider <jan at horde.org> (2012-03-26 11:26) 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?

The problem was that it was *not* wrapped in a dom:loaded event if  
called when output already started, even though it was supposed to.
This has been fixed with some of recent commits, it's properly wrapped  
again now.