Martin Höller

@melloware Ok, the topic is a bit more complex. So simple things first: the Showcase works as expected. My previous expectations were not completely correct. Sorry for this one. In...

@melloware I created an attachment with a reproducer: [primefaces-test-4485.tar.gz](https://github.com/primefaces/primefaces/files/10390123/primefaces-test-4485.tar.gz) I did not update the original description, as this is still the actual problem: state on server-side and in browser might...

Thanks for reopening! The documentation for `focusOnError` says: > Whether to focus the first tab that contains an error after form submission. In this simple use case the behavior is...

I understand your point. And I think I know how JSF works :wink: Anyway, having client- and server state out of sync doesn't sound promising to me and needs to...

Well, I think you got me wrong. When validation failed, DO NOT change state on server. Just make sure state on client is not changed! This means the tab which...

Hi @melloware! There is already a reproducer attached, reference here: https://github.com/primefaces/primefaces/issues/4485#issuecomment-1378401749_ Just unpack the file with `tar xzvf primefaces-test-4485.tar.gz`, change to new directory and run `mvn jetty:run-exploded`. After this, point...

Ok, I run your version and it seems client and server stay in sync now with `dynamic` enabled. Good. However it seems unintuitive to me, that the second tab is...

I tested your second version. The non-dynamic version seems to work as I expected. The dynamic-version works partly. It has problems when you do the following: 1) try to switch...

@melloware > Dynamic mode submits the form but loads 1 tab so you have no idea whether the error is on Tab1 or Tab5 or Tab99 because that is the...

Ahh! So if I get you right, the problem with the dynamic tab is only the update of the for the failed component? Well, this would have to be handled...