1 of 1 people found this helpful
Thank you for your post.
Pressing Escape or using a Close Popover step will leave the Popover button active. This is by design.
Even though the Popover is not in the tab order, keyboard navigation would be affected. There was consideration for leaving nothing focused, but then pressing the tab key would move back to the first field in the tab order.
Since you don't want the Popover button highlighted, using your workaround of Commit Records following Close Popover is correct.
I agree this is not EVER desirable behavior, so I'm surprised this was done by design. It can be worked around, but that means taking native, no scripting functionality and having to add a trigger/script for each popover. Too bad.
I would think that the keyboard navigation would be a lesser priority here, than the 'look' of the function. In Tom's case, he specifically has removed everything from the tab order, so enforcing 'keyboard navigation' in such a case is irrelevant.
How about a checkbox option on the popover settings? "Leave in focus on exit"?
And perhaps tab-order should remember whatever was 'previous tab' instead of whatever is the tab-order-of-the-current-object. So if you tab into an object and it has a tab order, that position is stored. Then the next press of the tab-key uses that stored value instead of just apparently referencing whatever the current object is. That would prevent the keyboard navigation issue you describe - although I'm sure it could raise other issues that I haven't thought of.
Thanks for the response, but I think this design decision should be revisited.
Look: if the popover button is not in the tab order, then the ONLY way to get to the popover is to click it, which means the next time you hit the tab key, you're going to go to the first field anyway! The exception is if you hit the Esc key to close the popover. This will focus the button, same as the script step. Again, this is IMHO the wrong design choice.
Please respect MY design choices as the database developer. If I wanted the button in the tab order I'd have put it in the tab order.
Should I submit this as a feature request?
I definitely recommend entering this suggestion to the Product Ideas board at: Product Ideas
The Product Ideas board is monitored by Product Management and Development. All suggestions are read, discussed and considered for possible implementation in a future release. Therefore, with the information I have supplied, be sure to explain your issue, and why this needs to be changed.