NVDA double reports focused object on startup #1359

Closed
nvaccessAuto opened this Issue Feb 9, 2011 · 4 comments

1 participant

@nvaccessAuto

Reported by aleksey_s on 2011-02-09 02:41
STR:

  • open "my computer"
  • navigate to any file
  • restart NVDA Current results: NVDA announces list item twice after restart. Expected results: NVDA should announce it only once.
@nvaccessAuto

Comment 1 by aleksey_s on 2011-02-09 02:42
This doesn't happen atleast in 2010.1.

@nvaccessAuto

Comment 2 by jteh on 2011-02-09 04:33
I investigated this a bit and I don't think there's much we can do. The issue is that a focus event gets fired after NVDA starts, but NVDA has already found and handled the focus itself. We don't eliminate it as a duplicate event because it is a child element, and since child elements don't have unique IDs, we must never treat them as duplicates.

I'm not sure why this wasn't a problem in 2010.1, as this code was included back then as well. The issue definitely exists in 2010.2. All I can think is that it might be timing related.

Deferring unless anyone has any particularly bright, workable ideas.
Changes:
Milestone changed from 2011.1 to near-term

@nvaccessAuto

Comment 3 by briang1 on 2011-02-09 07:37
I certainly cannot get it to occur in either of the 2010 releases, but the current snaps and the latest beas all do this. At first start up you definitely here
taskbar taskbar

Did someone change the order of initialising parts of nvda between the 2010 and 2011 versions so that it might miss the first message as it did not actually see it.
I take it this is a different issue to the multiple readin of some items that nvda has always done, like properties info etc?

@nvaccessAuto

Comment 4 by jteh on 2011-02-10 05:06
Brian: The taskbar issue is related, but slightly different.

Anyway, both of these cases are fixed by 95f5f86 and dc4db73.
Changes:
Milestone changed from near-term to 2011.1
State: closed

@nvaccessAuto nvaccessAuto added this to the 2011.1 milestone Nov 10, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment