Sébastien Lepage

PR was failing with recent changes, it has been reverted. Needs some investigation as of why it's been failing in 15

The current behavior is the right one, there is a very simple reason as of why there is this `disabledSelection` check once selection is submitted. Let's say, you have items...

This logic could also apply to `MenuButton`, right? If one item is contained in a MenuButton, could be rendered as a simple button... I realized I might be off topic...

I believe it is by design that even though components are not rendered, they're still part of the JSF tree therefore visited

Yeah I see what you mean, could be a question for https://github.com/jakartaee/faces

Since UIData from PF is based on UIData from Mojarra, I invite you again to ask to the specs guys here https://github.com/jakartaee/faces Depending what they say, we can do something...

Would be great to have a reproducer to know where your NPE comes from (meantime you can always give a stacktrace)

Sounds like the root cause is similar to this #9990.

If you have partial processing enabled, you're still required to process the table, therefore filter values should be available ?

> Our expectation is, that the expression filterValue="#{testView.currentGroupSelectionModel.availableGroupsFilterValues['displayName']}" should be evaluated, when the right side is updated for the updated data model. That's the issue? Or am I supposed to...