IAccessible2::WindowHandle property causes COM server exception when called out of process

VERIFIED FIXED

Status

()

Core
Disability Access APIs
VERIFIED FIXED
10 years ago
10 years ago

People

(Reporter: Michael Curran, Assigned: surkov)

Tracking

(Blocks: 1 bug, {access})

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(2 attachments)

(Reporter)

Description

10 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.8.1.11) Gecko/20071127 Firefox/2.0.0.11
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9b2pre) Gecko/2007120405 Minefield/3.0b2pre

Using NVDA screen reader this property always causes an exception. The first time it is called the call blocks for about 3 or so seconds and then causes the exception. Subsiquent calls cause the exception with no delay.
As NVDA uses IAccessible2 out of process for most things (excluding virtual buffers in future), I am unsure as to whether this property fails in process.
NVDA is able to call all the other supported IAccessible2 properties with no exceptions, only windowHandle causes problems. Windowhandle is also called the same way as all the other properties.
This bug has occured as far as I am aware ever since IAccessible2::WindowHandle was implemented. I did once report it was fixed though that was an error on my part with using a revision of NVDA that did not call IAccessible2::WindowHandle.
 NVDA is running in Python 2.5.1, using comtypes 0.4.1 to access COM interfaces. 
As I am still waiting for Accessibility Probe to become public, I can't test if the windowHandle property works ok in process / out of process with an accessibility testing tool.


Reproducible: Always
(Assignee)

Comment 1

10 years ago
Michael, how can I reproduce it?

Updated

10 years ago
Assignee: aaronleventhal → surkov.alexander
Blocks: 396346

Updated

10 years ago
Blocks: 368873
Keywords: access
(Reporter)

Comment 2

10 years ago
Created attachment 291819 [details]
A win32 c++ console mode program that locates a running Firefox3 and tests IAccessible2::WindowHandle on the client IAccessible2 object of the application window. zip file contains source code and com

On my system if I Open Firefox3 and then run the test program,  it finds the firefox window, gets the client IAccesible fine, gets the IAccessible2 fine, calls IAccessible2::States fine (to prove it works for other properties) but then fails on IAccessible2::WindowHandle
(Assignee)

Comment 3

10 years ago
When I run compiled program then I get an error:

Error querying service to IAccessible2 from IAccessible, code -2147221163

Michael, any idea?
(Reporter)

Comment 4

10 years ago
(In reply to comment #3)
> When I run compiled program then I get an error:
> 
> Error querying service to IAccessible2 from IAccessible, code -2147221163
> 
> Michael, any idea?
One of two things: 1. the program depends on the fact that only one program with an app window of MozillaUIWindowClass be running as it just uses the FindWindow win32 API call (so this would include not having Thunderbird or something else open). It was possibly trying to do things on the wrong app window.  2. You need to have an IAccessible2 proxy dll registered in Windows to actually have IAccessible2 working. If you don't have an IAccessible2 proxy dll I can provide you with one. Sorry, I just assumed you would have had this.
(Assignee)

Comment 5

10 years ago
Created attachment 291837 [details] [diff] [review]
patch
Attachment #291837 - Flags: review?(aaronleventhal)
(Assignee)

Updated

10 years ago
Status: UNCONFIRMED → ASSIGNED
Ever confirmed: true

Updated

10 years ago
Attachment #291837 - Flags: review?(aaronleventhal) → review+
(Assignee)

Updated

10 years ago
Attachment #291837 - Flags: approvalM10?
Comment on attachment 291837 [details] [diff] [review]
patch

a=drivers for when trunk opens after Fx3 Beta 2 freeze
Attachment #291837 - Flags: approvalM10?
Attachment #291837 - Flags: approvalM10-
Attachment #291837 - Flags: approval1.9+

Comment 7

10 years ago
Checked in for Surkov. Mick, this will be in the Dec 11, 2007 builds

Updated

10 years ago
Status: ASSIGNED → RESOLVED
Last Resolved: 10 years ago
Resolution: --- → FIXED

Comment 8

10 years ago
Verified using Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9b3) Gecko/2008020514 Firefox/3.0b3
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.