You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Sven Meier (JIRA)" <ji...@apache.org> on 2018/01/26 22:57:00 UTC
[jira] [Resolved] (WICKET-6517) use Ajax for multipart instead of
iframe
[ https://issues.apache.org/jira/browse/WICKET-6517?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sven Meier resolved WICKET-6517.
--------------------------------
Resolution: Fixed
Fix Version/s: 8.0.0
Many thanks to Andrew for this improvement!
> use Ajax for multipart instead of iframe
> ----------------------------------------
>
> Key: WICKET-6517
> URL: https://issues.apache.org/jira/browse/WICKET-6517
> Project: Wicket
> Issue Type: Improvement
> Components: wicket
> Affects Versions: 8.0.0-M8
> Reporter: Sven Meier
> Assignee: Sven Meier
> Priority: Minor
> Fix For: 8.0.0
>
>
> As Andrew Kondratev has pointed out on https://github.com/apache/wicket/pull/255, we can use FormData to send multipart data via Ajax. This makes the current iframe workaround obsolete.
> Advantages:
> - real Ajax !!1!!!
> - we can drop a lot of code in wicket-ajax-jquery.js
> - users can use Wicket.Ajax to send files as extra parameters, as requested in pull request #255
> FormData is supported in Edge and IE 10. I'm not sure whether we still support older browsers, but as fallback users can
> - continue using Wicket 7 (supported for the next years)
> - switch to non-Ajax uploads
> - use a polyfill for FormData (several available on github)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)