In a Notes database, the field tabbing works properly in Notes client for different forms. However, for the same database in Nomad, the tab only works for a few fields, and doesn't tab any further to the rest fields. I would think it's a Nomad PWA issue. Any ideas or recommendations to solve this problem? Much appreciated and a good day!
Tabbing between controls is a known issue that we are working to improve. In general, you will find that once you you tab to a PWA control (not one drawn directly to the canvas), you are stuck in the PWA controls until you click on another control. PWA controls are the combo box, list box, etc. that didn't have canvas renderings provided from the Notes core code and were done using React controls as the Nomad for web browsers implementations. But having the the mix of native, canvas controls and the PWA controls causes this tab sequence problem.
At this point, I doubt there is anything you can do about it (other than click to get to where you want to go). You will need for us to improve the tab keyboard sequence handling in the Nomad code.
Hey Rob, I'm just wondering if there has been any progress made on this? Is it on the ist of things to be worked on in a future release?
Thx in adance
Paul
It is on the list of things to work on in the future.
Thx Rob... don't mean to be pedantic, but is it scheduled to be available in a specific release, or is it in the enormous bucket of futures?
Latter.
Thx... appreciate your honesty.
This remains an issue for us in a dialogbox. When editing a document, tabs work fine, however, if we are in a dialogbox (NotesUIWorkspace.DialogBox) the tabs do not work.