Hi Laxman,
It sounds like you might not be properly attached. If you roll through the various spy methods, are you able to identify anything in Win32 or UIA? I've found that if UIA is the only thing that works well, usually that means I'm not really attached.
Chrome opens multiple processes with each new tab. I would check your attach stage to make sure you're attached to "chrome" process with a valid window title. If that doesn't fix it, try child index 0 or 1. For development purposes, if possible, try to have only one Chrome window and one Chrome tab open while spying elements (I know it's not always possible). If you still can't spy/highlight correctly and you've tried all of this and the other suggestions (reboot, etc.) you can try attaching via PID. It's a bit of a pain to do it, but there is an action for "read memory stats" in the environment utility. You pass in the "Chrome" process name and it will return a collection of process names and PIDs. PID is a valid input on the attach stage. You loop through the PIDs, attaching to each one, waiting for a valid element on the screen, the detaching if it's not found. Be careful to never attach to the PID = 0 (Idle Process). It'll lock up BP and you'll have to kill it.
Good luck and hope this helps!
------------------------------
Diane Sanzone
------------------------------
