Hi Michal,
The specification is silent on whether or not custom arguments are
supported or not. So it is undefined. If you can file an issue with a
reproducer that does not depend on RichFaces, but does show the problem
I could have look sometime in the next 2 weeks or so and see what can be
done.
Thanks!
Manfred
On 11/6/14, 5:53 PM, Michal Petrov wrote:
> Hi,
>
> I'm wondering what's the status quo regarding custom arguments in a request to server.
>
> This concerns jsf.js: In forms with enctype="multipart/form-data" when using FrameTransport only the standard arguments ("javax.faces.source", "javax.faces.partial.ajax", etc.) are let through (which was introduced as a fix for #2978).
> This breaks RichFaces functionality as we rely on custom arguments to be passed to the server as well. Are custom arguments supported, in which case is this behavior a bug? Or is this working as intended?
>
> Thanks,
> Michal Petrov
>