Sébastien Lepage

@tandraschko @melloware whenever you have some time, I'd like to hear from you on [my comment](https://github.com/primefaces/primefaces/issues/4278#issuecomment-443165936) and specially on this: > But the contract set by these methods are not...

Or, my "best" option is having something like this: ``` Map parameters = encodeMarkup(context, (T) component); encodeScript(context, (T) component, parameters); ``` `InputRenderer#encodeMarkup` returns whatever is needed for `InputRenderer#encodeScript`. I think...

Closing it for now, it seems with recent changes, community is fine with it 😢

ok

> it would be really nice to get rid of ui:repeat support but i think this is a heavy refactoring on how columnGroups works with filters. On the contrary, that's...

> it looks like that the facets (like filter) are stored per row-index instead of only one time. Can you ellaborate? What makes you think that? > Therefor we used...

Thank you for sharing those details. > Because the state map contains the component IDs of the filter's UIInput multiple times - including the rowIndex: f:dt:idOfFilter vs f:dt:0:idOfFilter, f:dt:1:idOfFilter, ......

The widget seems to have an option for that _(see url option)_: https://github.com/blueimp/jQuery-File-Upload/wiki/Options If you can investigate how to integrate in PF, would be great

See https://github.com/blueimp/jQuery-File-Upload/wiki/Upload-directly-to-S3 Regarding security reason, that is up to your CSP policy and not AJAX don't you think?

There can be a real advantage when you deal with big files, you're saving time by not copying the file on the webapp server, in few words: you're making one...