Reported by briang1 on 2011-02-12 13:23
This is a difficult one to explain, and may well be expected, but not by me!
Go to the snapshot download page in each browser.
Cursor down till you get the text will be made from this branch. Tab till you get the link to download.
In firefox this as expected will attempt to download the 2011.1 snap when you action the link
In IE it jumps back to the other downloads and tries to download the normal snap.
At least it does this on two machines here.
This works correctly in 2010.1, but fails in 2010.2 and current builds.
The correct behaviour, after looking at the settings is as Firefox.
The text was updated successfully, but these errors were encountered:
Comment 1 by briang1 on 2011-02-13 18:57
I note that the page in fact has content from sourceforge from just below the info about snapshots, till the end of the last item for downloading in both lists, including the text I use to position the cursor.
Interestingly, Webbie cannot cope with this page at all and leaves out the imported information completely.
However, one work around that does work in IE is to still position the cursor near where you want to be and use the direct K command and this ends up on the right link
Comment 2 by jteh on 2011-02-21 07:50
Technical: We now set focus to the nearest focusable ancestor. For content in frames, this is the frame document. Unfortunately, focusing a document causes NVDA not to override the tab key, as explained in ticket:720#comment:4:
VirtualBuffer._tabOverride is supposed to be used when tabbing in buffers if the cursor isn't within the focus. Unfortunately, when the focus is the document ..., everything will be considered to be within the focus.
Fixing the tab override code (#720) would fix this issue, but I still don't have any idea on how to do that yet. A simpler fix for this issue might be to just never focus documents. We already never focus the root document, so not focusing frame documents shouldn't do any harm. Mick, can you think of any reason this would be a problem?
Btw, the reason this problem doesn't affect Firefox 3.6 is, ironically enough, due to a bug in Firefox 3.6, which doesn't fire a focus event for frame documents. The problem does occur in Firefox 4.
Regression from 2010.1 (which didn't have focusableNVDAObjectAtStart).
Milestone changed from None to near-term