My guess is that, although vo doesn't show a virtual view of the pages to us, it does maintain such an internal view for it's own use.
I'd figure that somewhere during the page loading process, vo gets slightly confused on what's coming in, and it simply doesn't know what to do with itself. But, since it thinks it saw everything coming in, it believes there's nothing there, because it didn't see it. Compilers do this when punctuation is mismatched, it will sometimes think that you're typing in an extremely long string, until it either reaches max length, or finds what it thinks is the closing punctuation mark. I've had cases where c didn't point out my missing closing quote for several hundred lines. Admittedly, these kinds of issues are rare, but they are extremely hard to debug, and I'd guess something like that is happening here (not the missing punctuation) but the vo thinking it received something it didn't, or vice versa. And, as a result, it gets confused as to what it is seeing as opposed to what it should be seeing. If there was some way to force vo to reparce the data it has already received, this problem might be fixable simply by telling it to reaxmine what's on the screen.
Of course, it's not really that simple, but basically, that's the idea.If apple could provide us some method of refreshing the vo view of the current page content, wed be able to eliminate these kinds of errors.
Unfortunately, I have no idea how hard something like this would be for apple to do, but if it could be done, it would fix the issue nicely.
Click on the link below to go to our homepage. http://www.icanworkthisthing.com Manage your subscription by using the web interface on the link below. //www.freelists.org/list/macvoiceoverUsers can subscribe to this list by sending email to macvoiceover-request@xxxxxxxxxxxxx with 'subscribe' in the Subject field OR by logging into the Web interface at //www.freelists.org/list/macvoiceover
