Background:
There's been a bug in NVDA for years that when we load source copies of NVDA, events in browsers fail to talk to us. Somehow, I always ignored this in source, because core developers experienced it too, however, with the introduction of #7563 I believe this got much worse. Every time I update next, NVDA stops responding to dynamic events until I reboot. I can still nvda+f5 to refresh however.
Hypothesis
Since the library version is changing every time our version updates, somehow, the old code is receiving events and the new code isn't. There's something I think with this, because if I change from binary to source, and back to binary under proper working conditions, the path used to be the same, and the code would work just fine. I propose introducing a try build of NVDA that beeps upon every event responded to in a vbuff. That way, I can run that version installed, reboot, install next, then try to see if I get beeps, suggesting the old code is running.
Steps to reproduce:
Under any earlier than latest <next|master|you choose> build of NVDA
-
visit google.com.
-
type chickens into the search box.
-
now, go to the search box again, and type "horses"
Expected: you can press 2 to find search results for horses.
Actual: this works.
-
Now, repeat steps 1-3 again, after updating NVDA (So long as you have a binary version you are fine). Update to either latest next or master.
Expected: You get search results for Horses.
Actual: You get search results for Chickens, if you get search results for anything.
-
Now, press NVDA+f5.
Note how you now have search results for horses.
System configuration:
NVDA version: anything post #7563
NVDA Installed or portable: Needs to be a binary build, other than that it doesn't matter.
Does the issue still occur after restarting your PC? No
Have you tried any other versions of NVDA? I've tried source, and the several next builds.
Background:
There's been a bug in NVDA for years that when we load source copies of NVDA, events in browsers fail to talk to us. Somehow, I always ignored this in source, because core developers experienced it too, however, with the introduction of #7563 I believe this got much worse. Every time I update next, NVDA stops responding to dynamic events until I reboot. I can still nvda+f5 to refresh however.
Hypothesis
Since the library version is changing every time our version updates, somehow, the old code is receiving events and the new code isn't. There's something I think with this, because if I change from binary to source, and back to binary under proper working conditions, the path used to be the same, and the code would work just fine. I propose introducing a try build of NVDA that beeps upon every event responded to in a vbuff. That way, I can run that version installed, reboot, install next, then try to see if I get beeps, suggesting the old code is running.
Steps to reproduce:
Under any earlier than latest <next|master|you choose> build of NVDA
visit google.com.
type chickens into the search box.
now, go to the search box again, and type "horses"
Expected: you can press 2 to find search results for horses.
Actual: this works.
Now, repeat steps 1-3 again, after updating NVDA (So long as you have a binary version you are fine). Update to either latest next or master.
Expected: You get search results for Horses.
Actual: You get search results for Chickens, if you get search results for anything.
Now, press NVDA+f5.
Note how you now have search results for horses.
System configuration:
NVDA version: anything post #7563
NVDA Installed or portable: Needs to be a binary build, other than that it doesn't matter.
Does the issue still occur after restarting your PC? No
Have you tried any other versions of NVDA? I've tried source, and the several next builds.