You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Martin Grigorov (JIRA)" <ji...@apache.org> on 2011/01/18 10:22:43 UTC

[jira] Resolved: (WICKET-3345) Side effect induced by WICKET-2279 fix

     [ https://issues.apache.org/jira/browse/WICKET-3345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Martin Grigorov resolved WICKET-3345.
-------------------------------------

    Resolution: Cannot Reproduce

We cannot do much for now.
Please reopen the ticket when you have a quickstart application that reproduces the problem.
Thanks!

> Side effect induced by WICKET-2279 fix
> --------------------------------------
>
>                 Key: WICKET-3345
>                 URL: https://issues.apache.org/jira/browse/WICKET-3345
>             Project: Wicket
>          Issue Type: Bug
>          Components: wicket-extensions
>    Affects Versions: 1.4.12
>         Environment: IE8, windows7, Linux redhat
>            Reporter: Vincent MATHON
>            Priority: Minor
>
> This issue is directly related to https://issues.apache.org/jira/browse/WICKET-2279. 
> After a migration of Wicket-extension from 1.4.9 to 1.4.12, the  suggestions of some auto-complete fields in my application pages vanish after a few milliseconds.
> I don't understand exactly what happens since my pages are quite complexe but I solve my issue by replacing wicket-autocomplete.js version 1.4.12 with version 1.4.9 (I do 
> a hack in my application's wicket shared resources repository). Note that except this javascript file I use version 1.4.12 code (for Wicket, wicket-extension and so on).
> Thus, as  https://issues.apache.org/jira/browse/WICKET-2279 solves a bug but introduces also a new one, the piece of code involved should only be activable through an optional setting.
> Vincent MATHON

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.