[
https://issues.apache.org/jira/browse/WICKET-3323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12993591#comment-12993591
]
Hudson commented on WICKET-3323:
--------------------------------
Integrated in Apache Wicket 1.4.x #430 (See
[https://hudson.apache.org/hudson/job/Apache%20Wicket%201.4.x/430/])
WICKET-3323 TreeTable should call attachUpdate javascript on domready event.
Render 'Wicket.TreeTable.attachUpdate()' when DOM is ready, because otherwise
wicket-ajax.js could not be available yet
> TreeTable should call attachUpdate javascript on domready event.
> ----------------------------------------------------------------
>
> Key: WICKET-3323
> URL: https://issues.apache.org/jira/browse/WICKET-3323
> Project: Wicket
> Issue Type: Bug
> Components: wicket-extensions
> Affects Versions: 1.4.15
> Reporter: Alexander Morozov
> Assignee: Martin Grigorov
> Priority: Minor
> Fix For: 1.4.16, 1.5-RC2
>
> Attachments: fix-WICKET-1.4-3323.patch
>
>
> Since Wicket-1.4.15 it is possible to filter javascript resources
> (JavascriptFilteredIntoFooterHeaderResponse) and place them to the tail of
> HTML document. It means that some embedded javascript can be broken because
> of too early evaluation and missing dependencies.
> I have faced with this problem in TreeTable component. But probably there are
> other places in the framework, affected by this issue.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
