Sébastien Lepage

I can only agree with @christophs78. Not sure, if there is something else to be improved or not. Except that LazyDataModel#getRowData could expect a list of row keys instead of...

The motivation was certainly simplification of the feature. I understand on one side it's not ideal that getRowData is called n times, but as mentionned this could easily be fixed...

> That problem you mention also sounds reasonable but one can simple remove it from the selection attribute in the bean? It comes down the same as calling getRowData as...

Alright, I dug a bit on this. To sum up: - The problem is that selection gets lost after pagination, and used to work on 7.0 - As @christophs78 mentioned,...

See it this way, I select all my elements and doing nothing for the next 14 minutes (session timeout - 1) and then I do whatever I'm supposed to do...

Probably and as mentionned > There is a tiny difference how selection is handled though, in 7.0 selection used to be stored and restore from view state (see [DataTable#processUpdate](https://github.com/primefaces/primefaces/blob/45bb466d5a52707fa0542a0dbf68fb5ddcc8abc3/src/main/java/org/primefaces/component/datatable/DataTable.java#L294) and...

Yes I know, this is why I said "more or less all the input components". My thougths are, for: - multiple values (like PickList, Chips, Autocomplete etc.): display them with...

I started to work on something, I'll submit a PR to exchange ideas about this. CSS sounds like a lot of fiddling and it'll be a lot more easier to...

I just made a proposal (I didn't test everything, but just to give an idea of what it could look like). I only focused on InputRenderer kinda component (but that...

Yes, there will be an option in web.xml (disabled by default)