When I hit the tab button on my keyboard, I can tab exactly to the box I want and it takes 6 tab strokes to get there. When I try to put 6 tab strokes in my text blaze, it puts the cursor into a completely different box on the screen (it goes into the search bar at the top of the page!) and puts the text there instead. Why does tabbing manually on the page differ than text blaze's tabbing? Shouldn't the key stroke mimic exactly what I would be doing physically on my keyboard?
Hi @Marie_Hong and welcome to the forum.
In what app is this happening?
Please try using the {click} command and set the selector to the box you are trying to get to.
Does that work?
Hi and welcome @Marie_Hong ! In addition to what Dan said, please share a video if possible showing the issue.
Or, preferably, you can join a quick Google Meet call with me to check the issue. Please feel free to email me at gaurang@blaze.today
It was in chrome and using the click command worked! I am still wondering why tabbing is different between physically hitting the key and using the text blaze function, but thank you for finding a solution that works!
Glad it worked Marie! For some clarity, this likely happens because the focus is on a different element when the snippet is triggered, so the tabs jump to different elements. By using the {click} command, you specify which element should be focused and then the tabs work.