6.0.0-beta6
▾
Tasks
New Task
Search
Photos
Wiki
▾
Tickets
New Ticket
Search
dev.horde.org
Toggle Alerts Log
Help
4/10/26
H
istory
A
ttachments
C
omment
W
atch
Download
Comment on [#11099] Incorrect order of javascript
*
Your Email Address
*
Spam protection
Enter the letters below:
.__..___.. . .. , | | | | |_/ \./ |__\ | |___| \ |
Comment
>>> 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.
Attachment
Watch this ticket
N
ew Ticket
M
y Tickets
S
earch
Q
uery Builder
R
eports
Saved Queries
Open Bugs
Bugs waiting for Feedback
Open Bugs in Releases
Open Enhancements
Enhancements waiting for Feedback
Bugs with Patches
Enhancements with Patches
Release Showstoppers
Stalled Tickets
New Tickets
Horde 5 Showstoppers