*This post is locked for comments
*This post is locked for comments
We saw the behaviour relating to working with Visual Studio Tools addins. In our case, the Microsoft Communicator integration.
There is a workaround fix that we tried that worked. If you log a support case, you can mention bug 46619.
David
David - thanks for the reply. You mentioned having seen similar "weird" tabbing issues but have not been able to track down the cause. At this point do you see any value in having me open a support incident for my customer?
- Darren
Hi Darren
I have seen some weird issues where tabbing fails to leave a field. Have not been able to track down the cause yet.
We used the Support Debugging Tool to capture the scripts running when tab was pressed and it did not give us anything of value.
The Support Debugging Tool helps us find when code written in Dexterity does unexpected things, but it cannot help much when Dexterity itself does unexpected things.
David
Developer of Support Debugging Tool.
What's the user preference for accessing each field? Tab or Enter?
The form is not modified. In fact, the tabbing issue is experienced in more than one window (all of which are not modified); the Summary Inquiry window I mentioned in my post is just one example.
Is this a modified form? Have you tried renaming the forms dictionary and testing the tab sequence that way? (if you remove the forms dictionary, you will need to revert security to the original forms).
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
André Arnaud de Cal... 291,280 Super User 2024 Season 2
Martin Dráb 230,235 Most Valuable Professional
nmaenpaa 101,156