-
Notifications
You must be signed in to change notification settings - Fork 298
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
InMethod TreeGrid doesn't properly react to clicks after opening a closed subtree #513
Comments
After the Ajax request, the newly visible table rows do not have the onclick-Handler that should be supplied by the AjaxFormSubmitBehavior which is added to each table row by AbstractGrid. I do not yet know why this is, but both in the Chrome debugger and in Firebug I can see that the original table rows have this onclick-handler, the new ones don't. |
Interestingly, it seems only to happen in master. The wicket-6.x branch works correctly. Still investigating. |
I'm still investigating this. I can see that in the the event handlers are not showing up, but in the full page refresh they are there. I'm trying to |
This is related to wicketstuff/wicket1.5-tree#3. |
I found a fix for the bug in wicket1.5-tree (wicketstuff/wicket1.5-tree#4). Once that is accepted and merged, inmethod-grid could be updated. I already tried it locally, it works by simply updating that dependency. |
…on with opening tree nodes via ajax
…-tree upgrade to wicket15-tree 7.1.0 to fix issue #513, regression with ope…
When running e.g. the inmethodgrid-examples, newly-displayed rows after opening a closed subtree do not react to clicks. In the demo, neither selecting such items in "Tree Grid with item selection" nor editing such items in "Editable TreeGrid" works.
Workaround: After manually refreshing (F5) the page, it works for those items. Items that are in other subtrees that get opened later need another refresh to work. This is rather awkward for the users.
I suspect that some JavaScript event handlers do not get properly attached by the AJAX response to the click on the "open subtree" icon. I'm investigating it, but it would be great if someone more familiar with this component could have a look too.
The text was updated successfully, but these errors were encountered: