Skip to content


Subversion checkout URL

You can clone with
Download ZIP


NVDA not rendering all content in virtual buffers in Firefox #2168

nvaccessAuto opened this Issue · 3 comments

1 participant


Reported by KevanGC on 2012-03-15 09:18
NVDA 2011.3, with Firefox 11.

STR: Go to and search for anything.

Expected: NVDA should read the book search results after the filter options.
Actual: The virtual buffer contains no book search results, but they are shown. Switching to focus mode and tabbing on the last filter does cause NVDA to read them, although it's difficult to navigate that way.

Luckily I still have the setup file to Firefox 3.6, so I was able to switch back to that and things work nicely. I'm not sure what version of Firefox this problem began in, but it would be amazing if you could get it fixed if it's an NVDA issue. Audible probably isn't the only site where NVDA won't read all the content, I just got Firefox 11 today and haven't found any other sites with the problem, but if it happens on Audible, it can happen anywhere else.


Comment 1 by briang1 on 2012-03-15 15:03
I cannot see this effect using XP and ff11. However It does seem to put the cursor position on the bottom of the list rather than the top for some reason after a search. Of course having no sight and not knowing the site, it could be that stuff is missing but I certainly get a list of items that are connected to my search with the usual listen and buy stuff on links.
I also tried ff3.68 and IE8 and they seem to act more or less the same. I tried it with the rc1 and the 2011.3 versions of nvda and the latest snap as well.


Comment 2 by jteh on 2012-03-15 22:16
I suspect this is a duplicate of #2059. Please try again with Firefox maximised if it isn't already. Failing that, please try with Firefox 12pre.


Comment 3 by jteh on 2012-08-14 06:50
Closing as a duplicate of #2059 (fixed in Firefox 12). If you can still reproduce this with recent Firefox versions, please reopen.
Added labels: duplicate
State: closed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.