Closed Bug 617084 Opened 14 years ago Closed 14 years ago

When using the BACK function, NVDA's virtual buffer doesn't get updated any more

Categories

(Core :: Disability Access APIs, defect)

defect
Not set
major

Tracking

()

VERIFIED WORKSFORME

People

(Reporter: MarcoZ, Unassigned)

References

Details

(Keywords: regression)

STR: 1. Open a current Minefield build with NVDA. 2. Open www.mozilla.com. 3. Navigate to the "About" link and press Enter. Result: NVDA will start reading the About Us page of Mozilla.com. 4. Stop NVDA's reading with CTRL, then presss Alt+LeftArrow to get back to the previous page. Expected: NVDA should announce that the document is loading, and that the focus lands on the About link. Actual: Nothing happens. NVDA does not speak anything. 5. Press NVDA+F5. Result: Nvda will speak "Refresh", followed by "unknown", and focus will land somewhere, next interaction will most likely be the Location bar. 6. Now, grab the try-server build from Bug 498015, and perform the above steps again. Result: NVDA will speak the focus change to the About lik after step 4, and performing step 5 isn't necessary. But: 7. With that same try-server build, press either Ctrl+T to open a new tab, or Ctrl+N to open a new window, doesn't matter. 8. Go to http://www.mozilla.org (the Foundation homepage). 9. Choose the About link with the Arrow keys and hit Enter. 10 After NVDA starts reading, stop with CTRL. Now press Alt+Left again. Result: The behavior in this second tab or window is now exactly the same as observed after step 4 above in the nightly build. So, bug 498015's current try makes this situation a little better, but not back to a fully working state as in Firefox 3.6.
(In reply to comment #0) > 7. With that same try-server build, press either Ctrl+T to open a new tab, or > Ctrl+N to open a new window, doesn't matter. > 8. Go to http://www.mozilla.org (the Foundation homepage). > 9. Choose the About link with the Arrow keys and hit Enter. > 10 After NVDA starts reading, stop with CTRL. Now press Alt+Left again. > Result: The behavior in this second tab or window is now exactly the same as > observed after step 4 above in the nightly build. I'm guessing this is bug 610985.
(In reply to comment #1) > I'm guessing this is bug 610985. Given bug 610985 comment #6, I no longer think this is the case. That bug only affects events updating a buffer. It shouldn't affect the loading of new documents.
Marco, is it valid still?
Works for me in Mozilla/5.0 (Windows NT 6.1; WOW64; rv:2.0) Gecko/20100101 Firefox/4.0
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → WORKSFORME
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.