Yeah I guess this works fine, thanks.
However, regarding the initial premise of using a user widget button instead of a regular button, I found an issue.
when you’re using arrow keys to navigate, and you need to set up explicit navigation for the bottom button to go back to the top on arrow down (and similar for the top button), it works fine with regular buttons, but not quite with user created button widgets.
After navigating to any explicitly set button, the interaction input key (such as space bar, enter, etc) won’t work, it won’t interact with the button, even though is has keyboard focus.
If you move from the first button to the second button, as in the standard navigation flow that doesn’t need any explicit mapping, it still works fine, but the previous issue is kind of a deal breaker. is there any way to fix this behavior?
I think the issue might be that the explicit mapping might be focusing on the entire user widget (button and text as a whole) instead of specifically the button.