You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Janne Hietamäki (JIRA)" <ji...@apache.org> on 2007/05/16 06:48:16 UTC

[jira] Resolved: (WICKET-573) Autocomplete field cuts off parameter in Non-IE Browsers

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

Janne Hietamäki resolved WICKET-573.
------------------------------------

       Resolution: Duplicate
    Fix Version/s: 1.3.0-beta1

This is duplicate of WICKET-425, and has already been fixed in wicket 1.3.

See https://issues.apache.org/jira/browse/WICKET-425 for more details.



> Autocomplete field cuts off parameter in Non-IE Browsers
> --------------------------------------------------------
>
>                 Key: WICKET-573
>                 URL: https://issues.apache.org/jira/browse/WICKET-573
>             Project: Wicket
>          Issue Type: Bug
>          Components: wicket-extensions
>    Affects Versions: 1.2.5, 1.2.6, 1.3.0-beta1
>         Environment: Firefox 2, Fedora Core 6
>            Reporter: Dan Syrstad
>         Assigned To: Janne Hietamäki
>             Fix For: 1.3.0-beta1
>
>
> AutoCompleteTextField.getChoices(String input) receives a truncated input parameter when the input contains a special URI character such as "&" or "%".  This happens only in Firefox (really any non-IE browser). IE works fine.
> For example, if you enter "D & B Company" in the field, getChoices() only receives "D " (truncated at the "&").
> This is a bug in wicket-autocomplete.js processValue(). Changing this function to comment-out the IE-specific code fixes it:
>     function processValue(param) {
>         //var browserName = navigator.appName;
>         //if (browserName != "Microsoft Internet Explorer"){  
>         //    return param;
>         //}
>         return encodeURIComponent(param);
>     }
> This causes encodeURIComponent() to always be called regardless of the browser. This seems to fix the problem for IE 6 and Firefox. I'm not sure what affect this might have in other browsers such as Safari, Opera, or earlier IE browsers.

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