XML UI InputFields: unexpected behavior with "tab" key navigation under certain circumstances#2194

I have created a Global XML UI layout that has a TON of InputField boxes on it. Using the “selectOnDown” attribute, I have setup which InputField gets the focus with each tab key press (pressing tab takes the focus to the next element to the right of the current element instead of directly down). This is behaving correctly, UNLESS I add any XML UI to any object.
The behavior I’m seeing when any XML elements exist on any object (in addition to my global layout) is that a single tab key press seems to get registered more than once, eg: pressing the tab key once causes the InputField element that is 2, 3, or 4 elements away (instead of the next one) to get the focus.
Even more bizarre, is that the number of extraneous unintended tab key mimics increases proportionately with the number of times I save/play (from Atom).
Let’s say that ‘x’ equals the number of elements that are being unintentionally skipped by pushing the tab key only once.
x starts off as 0. x= 0
So, when I first load up my mod, and use the tab key to navigate among my InputField elements, there is no issue. x=0, and no elements are being skipped.
If I save/play one time, now x=1, and one InputField element gets skipped so that instead of the very next InputField getting the focus, it skips that one and goes to the one after (goes every other).
If I save/play a second time, now x=2, and TWO InputField elements get skipped.
x increases by 1 with every save/play, so that after 10 save/plays, 10 elements get skipped with every tab press instead of the focus going to the very next element.

Edit:
I forgot to mention that this issue still occurs even if all the xml on the object is commented out. All data/text/xml needs to be removed from the xml file for the object in order for this issue to NOT occur.

This issue also occurs when using object.UI.setXml() in global. Even if I set it to wait 10 seconds before setting the xml. For example, when I load up the mod initially, the bug isn’t present, but after 10 seconds when I have setXml on the object, the bug suddenly is there.

And this issue persists across different mods, and only resets itself when exiting to the main menu. If I load up mod a, save/play a couple times, and then immediately load up mod b, mod b experiences the bug.