-
Notifications
You must be signed in to change notification settings - Fork 762
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
DataTable: addRow() widget method should use partialSubmit and avoid posting all inputs #3564
Comments
Close in favor of: #3571 |
First of all, this has nothing to do with the EditableDatatable. It happens for a normal datatable with inputs as well. I've analyzed all this and the addRow by default processes the children of the datatable but submits the whole surrounding form (the default if nothing else is specified)
By changing the This might however break existing functionality since if I remember correctly, in IE the blur/click events might be in a different order, so the submission of the editable input in the onblur event might occur after clicking a button that does an 'addRow()'. So maybe an additional |
So I vote to re-open this. It is as stated NOT related to an editableDataTable and removing that from the title makes it a generic issue. |
I think you need a process=datatable, so that the datatable can trigger teh AddRowFeature. |
The addRowFeature seems to be working without it... I checked live in the showcase. The feature is triggered by a special parameter in the request https://github.com/primefaces/primefaces/blob/master/src/main/java/org/primefaces/component/datatable/feature/AddRowFeature.java#L52 which still is there (form%3Acars2_addrow=true for the showcase)! But I'll check never the less... |
The AddRowFeature is normally called, so it is a fix... maybe the 'skipChildren' attribute of the datatable can be used as well to do a 'partialSubmit' by default or not... |
I will close it for now. No work done here and #3571 would be the real way IMO. |
No description provided.
The text was updated successfully, but these errors were encountered: