I donโt know if this is related, but I had a similar problem when the tabindex property of the web form did not work by pressing the TAB key, after focusing on the first input when loading the page, until the user first clicked on the form with the mouse.
I did not have access to the source code, so I tried to solve it using javascript.
Before the first mouse click, all keystrokes, including the TAB key, triggered a keystroke event, the TAB key was not detected by pressing the / keyup key when the page loaded.
I found out that the TAB key triggered a key press event, and I could access the key code through it. just by logging a keystroke event and manually switching to the next input with jQuery processed. after the first mouse click, the form behaved as expected, the TAB key was no longer infected with the keypress event.
here is a sample code:
function tabNext(e){ if(e.keyCode == 9){
source share