You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Reported by dgoldfield on 2010-10-08 12:50
I am using Seamonkey 2.0.8. If I go to www.facebook.com with this browser NVDA's virtual buffer only shows the first two or three lines of the page, when I use my arrow keys, ending with the line that says "chat 0." However, if I use the tab key I am able to move through the various links and form controls. I even hear NVDA play the camera sound when moving into an edit box indicating that I am temporarily out of browse mode. I think I was once able to get NVDA to display the full page by restarting NVDA, but this is not consistent and the last time I tried doing that the virtual buffer still only let me read the first few lines using arrow keys. This is a relatively new problem and it may have started with Seamonkey's latest version.
The text was updated successfully, but these errors were encountered:
This issue is abandoned for more than six years, furthermore, Facebook has changed multiple times since then. Closing. If this is still the case, please provide a new issue with steps to reproduce, and at least try to reproduce with multiple browsers.
Reported by dgoldfield on 2010-10-08 12:50
I am using Seamonkey 2.0.8. If I go to www.facebook.com with this browser NVDA's virtual buffer only shows the first two or three lines of the page, when I use my arrow keys, ending with the line that says "chat 0." However, if I use the tab key I am able to move through the various links and form controls. I even hear NVDA play the camera sound when moving into an edit box indicating that I am temporarily out of browse mode. I think I was once able to get NVDA to display the full page by restarting NVDA, but this is not consistent and the last time I tried doing that the virtual buffer still only let me read the first few lines using arrow keys. This is a relatively new problem and it may have started with Seamonkey's latest version.
The text was updated successfully, but these errors were encountered: