DOM node focus lost on set to disabled but Focus remains on Focusable Element

[stuartflanagan]

Describe the bug
When using shouldFocusDOMNode initial focus works as expected. If for some reason actual focus is lost. This happens if a button element is set to disabled while fetching data or a mouse click in another area of the DOM via LG Magic Remote, then focus remains on the button from useFocusable but the underlying DOM node has lost focus.

To Reproduce
Steps to reproduce the behavior:

1. Set new INIT with shouldFocusDOMNode true.
2. Create a focusable element with useFocusable with a button
3. Programatically set button element to disabled: true and then back to disabled: false
4. The focus still appears to be on the correct Button but no onEnterPress methods will fire.

Expected behavior
Expect visual focus and focused property from useFocusable to reflect actual state.

I assume this is not trivial to do, as the DOM focus is not tracked as part of the library.

Screenshots
If applicable, add screenshots to help explain your problem.

Additional context
Add any other context about the problem here.

[stuartflanagan]

Hello, Just wondering if there might be any advice on synchronising the blur of an element and the blur of a focusable element?

[stuartflanagan]

This is still an issue and wondering if anyone has any ideas on how to address this. It seems that focused should return false when this occurs?