[
https://issues.apache.org/jira/browse/WICKET-2252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12705950#action_12705950
]
Per Cederberg commented on WICKET-2252:
---------------------------------------
Should work ok, since our patched source code no longer shows any diff on this.
Thanks!
> Autocomplete text fields don't call existing JavaScript event handlers
> properly
> -------------------------------------------------------------------------------
>
> Key: WICKET-2252
> URL: https://issues.apache.org/jira/browse/WICKET-2252
> Project: Wicket
> Issue Type: Bug
> Components: wicket-extensions
> Affects Versions: 1.3.6, 1.4-RC2
> Reporter: Per Cederberg
> Assignee: Igor Vaynberg
> Priority: Minor
> Fix For: 1.3.7
>
>
> The Wicket AutocompleteTextField component attaches to an INPUT HTML element.
> In doing so, it replaces several JavaScript event handlers, such as
> "onclick", "onblur", etc. It also stores the previous callback handlers and
> attempts to ensure that they are called whenever the appropriate event
> occurs. But the logic for this is unfortunately somewhat flawed in Firefox,
> Safari and Opera browsers, since the original DOM event object is lost.
> The proper fix requires changing code like this:
> if(typeof objonchangeoriginal=="function")objonchangeoriginal();
> into the appropriate call:
> if(typeof
> objonchangeoriginal=="function")objonchangeoriginal.apply(this,[event]);
> As of version 1.3.6 of Wicket, the following event handler calls should be
> fixed like this:
> objonchangeoriginal
> objonblur
> objonfocus
> objonchange
> objonkeydown
> objonkeyup
> objonkeypress
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
