You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Marco Springer (JIRA)" <ji...@apache.org> on 2012/08/16 09:49:38 UTC
[jira] [Updated] (WICKET-4711) Ajax file upload bug in Opera
[ https://issues.apache.org/jira/browse/WICKET-4711?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marco Springer updated WICKET-4711:
-----------------------------------
Attachment: ajaxupload.zip
Contains the bare minimum, only an upload form the an upload field and the ajax button.
When a file is uploaded, only the file name is printed out in the console.
It's only to demonstrate the ajax behavior and the error when using Opera 12.01
> Ajax file upload bug in Opera
> -----------------------------
>
> Key: WICKET-4711
> URL: https://issues.apache.org/jira/browse/WICKET-4711
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 1.5.7
> Environment: Linux (Ubuntu 12.04 with KDE as DE)
> Opera 12.01 as browser
> Reporter: Marco Springer
> Attachments: ajaxupload.zip
>
>
> When I submit a Form that contains a FileUploadField component and a simple AjaxButton, I receive a message in the Wicket Debug window in the browser that states the following:
> INFO: focus set on submit4d
> INFO: Invoking pre-call handler(s)...
> ERROR: Wicket.Ajax.Call.failure: Error while parsing response: Could not find root <ajax-response> element
> INFO: Invoking post-call handler(s)...
> INFO: Invoking failure handler(s)...
> This relates back to calling setMultiPart(true); on the form, which is automatically done when adding a FileUploadField.
> When this is set to true, the above problem ocurred.
> I only get this when using Opera (currently using 12.01).
> Firefox 14.0.1, Konqueror 4.8.4 and Chromium 18.0.1025.168 work fine.
> This is reproduceable when using the wicket examples:
> http://www.wicket-library.com/wicket-examples/ajax/upload
> Thanks in advance.
> Cheers,
> Marco
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira