Comment 1 by parham on 2012-04-04 07:12
I have reported this previously. Apparently, NVDA gets sent the focus from the browser a little later. This causes NVDA to jump back to where it should have focussed a second ago. This is still not fixed, and happens in websites with a lot of processing power needed because of Javascript (for example, Google docs, GMail, Facebook, etc). I'm not sure if there can be a fix for this now, but back then, as far as I understood, there couldn't be.

Comment 2 by briang1 on 2012-04-04 08:20
Have you got a web page that does not require you to be in webmail or log into a site that shows this problem?

I did have some odd issues with the search engine startpage.com where sometimes a search would make the system focus on an apparently random point in the list of results sometimes.

Also if you raised a ticket before, what was its number as I could not find it.

I have not got Chrome, but I have Firefox and IE8, and apart from the above mentioned have not seen this effect on normal web pages. Some pages are sluggish if they have lots of javascript.

Comment 3 by kredh on 2012-04-04 08:44
You may be able to see this on a Google search pressing quickly the H arrow key to navigate between titles. Though, it may depend on the system resources and websites that have this problem all the time need to log in, as Gmail (browse the e-mails tab) or Facebook.

Comment 4 by briang1 on 2012-04-05 06:44
The reason I brought up logging in is that often in these pages, you get at least part of the page delivered over a secure system, and this can make the page slower to refresh. This is I suspect the key issue that causes the problem.

Comment 5 by parham on 2012-04-05 07:32
I was speaking about this in ticket:2039

Comment 6 by jscuster on 2012-04-05 20:00
Thank you all for your comments, I wondered when this ticket would be seen.

Comment 7 by jscuster (in reply to comment 1) on 2012-04-05 20:02
Replying to parham:
Oh, I understand, thank you. I do have a dual-core 1 ghz netbook with 4 gb ram. I also had a 1.66 GHZ dual-core with 1 GB ram. Both experienced the same problem.

I have reported this previously. Apparently, NVDA gets sent the focus from the browser a little later. This causes NVDA to jump back to where it should have focussed a second ago. This is still not fixed, and happens in websites with a lot of processing power needed because of Javascript (for example, Google docs, GMail, Facebook, etc). I'm not sure if there can be a fix for this now, but back then, as far as I understood, there couldn't be.

Comment 8 by jscuster (in reply to comment 2) on 2012-04-05 21:15
Replying to briang1:

Have you got a web page that does not require you to be in webmail or log into a site that shows this problem?

I did have some odd issues with the search engine startpage.com where sometimes a search would make the system focus on an apparently random point in the list of results sometimes.

Also if you raised a ticket before, what was its number as I could not find it.

I have not got Chrome, but I have Firefox and IE8, and apart from the above mentioned have not seen this effect on normal web pages. Some pages are sluggish if they have lots of javascript.

yes, I do have another site. As kredh suggests, google.com displays this problem nicely. I did a search using firefox, searching for: "how to eat apples" and experienced the problem. Note, It wasn't every time I tried to move quickly through the results, but it happens after trying it a few times. Chrome displays this problem even better than the other browsers, but the big 3 do show this problem. This is my first ticket on the issue.

Comment 9 by jscuster (in reply to comment 5) on 2012-04-05 21:21
Replying to parham:
I'm sorry, I didn't see that ticket, though I did search for other tickets. I notice that 2039 is listed as an enhancement, not a defect. This seems like a defect to me. Also, 2039 only lists facebook, but this problem is on several sites. Perhaps the two can be integrated? Sorry for the error on my part.

I was speaking about this in ticket:2039

Comment 10 by jteh on 2012-04-05 23:53
Closing as duplicate of #2039, though I understand this isn't obvious.
Changes:
Added labels: duplicate
State: closed

Comment 11 by jscuster on 2012-04-06 02:42
OK, I understand and agree. I would just like to point out two observations.

1. 2039 deals with unresponsiveness, where 2211 deals with jumping cursors. As I have indicated earlier, I believe the solution to one prob will solve the other, I just want to reiterate this difference.
2. 2039 hasn't had any attention for 3 months, I hope it will get some attention, and I hope it will be changed from enhancement to defect. I would change it myself, but I understand that the decision was made and I don't know the reasons behind it. Also, I understand there are higher priority items which need attention too, so please don't think this is a rant, it's not intended as one.

Thank you all again for taking interest in this.