[
https://issues.apache.org/jira/browse/WICKET-5229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13683291#comment-13683291
]
Sven Meier commented on WICKET-5229:
------------------------------------
IMHO the old solution was due for an overhaul:
// re-attach the events to the new components (a bit blunt method...)
// This should be changed for IE See comments in wicket-event.js add
(attachEvent/detachEvent)
// IE this will cause double events for everything.. (mostly because of
the jQuery.proxy(element))
Wicket.Focus.attachFocusEvent();
Note that if a developer uses #stopImmediately from his "focus" event handler,
this would break Wicket's focus tracking too.
> use jquery "focusin"/"focusout" for ajax focus tracking
> -------------------------------------------------------
>
> Key: WICKET-5229
> URL: https://issues.apache.org/jira/browse/WICKET-5229
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 7.0.0
> Reporter: Sven Meier
> Assignee: Sven Meier
> Fix For: 7.0.0
>
>
> Focus tracking in wicket-ajax-jquery.js can be simplified with jQuery
> bubbling "focusin"/"focusout".
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
