Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Firefox 4.2a1pre x64: virtual buffer always empty #1454

Closed
nvaccessAuto opened this issue Apr 12, 2011 · 10 comments
Closed

Firefox 4.2a1pre x64: virtual buffer always empty #1454

nvaccessAuto opened this issue Apr 12, 2011 · 10 comments

Comments

@nvaccessAuto
Copy link

Reported by kevinchao89 on 2011-04-12 02:22
NVDA Snapshot 4160
Firefox 4.2a1pre x64 (2011-03-29)
Bringing up Firefox 4.2a1pre x64, any website.
UP/DOWN ARROWS report blank
LEFT/RIGHT ARROWS report an error tone (same one that's issued with snapshots/pre-release when page hasn't finished loading)
Elements list is blank/empty
TAB and SHIFT+TAB work to go to next/previous element.

@nvaccessAuto
Copy link
Author

Comment 1 by jteh on 2011-04-12 04:18
First, it's worth noting that Firefox accessibility is not safe in 64 bit builds. Even though it seems to work (excluding buffers), it may fail randomly depending on your memory usage. This is MozillaBug:606080.

However, this seems to be a different problem.

Technical: It looks like !AccessibleObjectFromEvent is failing in-process, but works fine out-of-process. In-process, it seems to just return an oleacc client object instead of the Firefox root accessible. I have no idea why this would be the case. I need to write a test case to confirm this.
Changes:
Changed title from "Firefox 4.2a1pre x64: arrows and elements list don't work" to "Firefox 4.2a1pre x64: virtual buffer always empty"

@nvaccessAuto
Copy link
Author

Comment 2 by jteh on 2011-04-12 05:21
Filed MozillaBug:649236.

@nvaccessAuto
Copy link
Author

Comment 3 by mdcurran on 2011-06-17 14:00
Fixed in d1fac5b. Seems to be a bug in AccessibleObjectFromWindow when called from a 64 bit application (not sure if the bug is limited to a window in the same thread).
Changes:
Milestone changed from None to 2011.2
State: closed

@nvaccessAuto
Copy link
Author

Comment 4 by mdcurran on 2011-06-17 14:08
Note that although this fix now gets around the AccessibleObjectFromWindow case, Mozilla Gecko accessibility still may have issues with its unique IDs as they are based on pointers (which may overflow in 64 bit memory as childIDs are 32 bit). But I don't really see how the AccessibleObjectFromWindow bug was at all related to the quoted mozilla bug (overflow of unique IDs).

@nvaccessAuto
Copy link
Author

Comment 5 by mdcurran on 2011-06-17 14:15
Aa, ignore the last sentence in my last comment, I see there are two separate Mozilla bugs. :)

@nvaccessAuto
Copy link
Author

Comment 6 by jteh on 2011-06-18 06:39
Should we revert this given that you discovered that this is in fact a Gecko bug? I'm reluctant to have unnecessary work around code, especially as official 64 bit builds of final releases are not provided.

@nvaccessAuto
Copy link
Author

Comment 7 by mdcurran on 2011-06-18 07:08
I guess so.

@nvaccessAuto
Copy link
Author

Comment 8 by mdcurran on 2011-06-18 07:16
Reverted d1fac5b as I have identified now that the bug is Gecko's, and since no official 64 bit Gecko builds are out yet, and because it would only be a change of one line for Gecko, I think this is pretty certain that the fix should get in. Re opening as it now depends on an external fix again.
Changes:
State: reopened

@nvaccessAuto
Copy link
Author

Comment 9 by jteh on 2011-06-19 00:33
Changes:
Milestone changed from 2011.2 to near-term

@nvaccessAuto
Copy link
Author

Comment 10 by jteh on 2012-01-06 05:06
MozillaBug:649236 has been fixed.
Changes:
State: closed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant