On Sun, Feb 7, 2021 at 10:42 AM, Aravind R wrote:
its due to brouser nav nvda add on which i found out just now.-
And this is precisely why one of the earliest steps in doing "issue related" debugging is restarting NVDA with add-ons disabled. It's simple to do, and if the issue vanishes then you have confirmation that it's with an add-on, not NVDA itself.
Then, depending on how many add-ons you have, you go through the process of disabling them all in add-ons manager, then re-enabling them either one at a time (if you have only a couple) or in groups until the issue reappears. If you were doing one-by-one reenabling, you instantly know your culprit. If you were doing groups, you know the group it's in, disable those all again, and reenable one-by-one to find out which one in the group is the culprit.
Brian - Windows 10 Pro, 64-Bit, Version 20H2, Build 19042
The depths of denial one can be pushed to by outside forces of disapproval can make you not even recognize yourself to yourself.
~ Brian Vogel