Sven Jansen

@melloware The Reason for that behavior lies inside the `TableBody.js : 456 - focusOnElement` called by `TableBody.js : 299- onMultipleSelection `. There you got that snipped: ```js if (isCheckboxSelectionModeInColumn) {...

I'm not sure what the original idea was; however, I cannot see any value for it here. As mentioned, if you use keyboard navigation, the table already focuses on the...

@melloware seems not to be similar. You fixed #6035 in #6036 but this problem here is still there in `10.6.6`

I disagree. See my [comment](https://github.com/primefaces/primereact/issues/6755#issuecomment-2177825783) in @jerlam06 issue #6755 Even at [react.dev docs](https://react.dev/learn/sharing-state-between-components) they do it [the way PrimeReact is doing](https://codesandbox.io/p/sandbox/react-dev-kyxl65?utm_medium=sandpack) it.

I noticed that this is not an error. My problem here is noted in the docs: > If optionValue is omitted and the object has no value property, the object...

That works, and I'm using it in other parts of my code. However, now if I need to work with that object, for example, in the onChange event, I need...

@Rekl0w, I see your point; however, it feels wrong that the component works differently based on how something looks inside. If I pass, for example, `[{foo: "label", bar: "value"}, {foo:...

I would expect that if I do not set optionValue, that I get back whatever I throw in.

@melloware just looked at the code ````js const getOptionValue = (option) => { return props.optionValue ? ObjectUtils.resolveFieldData(option, props.optionValue) : ObjectUtils.resolveFieldData(option, 'value') || option; }; ```` The question I have here...

I don't really understand what exactly you're doing there. However, I don't think that this is something PrimeReact could fix. Why are you doing things so complicated? Just do something...