Closed Bug 297069 Opened 19 years ago Closed 17 years ago

Windows opened with |Firefox -chrome myfile.xul| are not accessible

Categories

(Core :: Disability Access APIs, defect)

x86
Windows XP
defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 241015

People

(Reporter: parente, Unassigned)

References

Details

(Keywords: access)

Application nodes in the MSAA DOM do not always report their children propertly.

For instance, 

firefox -chrome file://c:/parente/mozilla/rdf/resources/dom-test-4.xul

lists it child widgets properly but 

firefox -chrome file://c:/parente/mozilla/rdf/resources/dom-test-8.xul

does not.

For applications that do not list their children, the following exception is 
reported for each child:

* Call to xpconnect wrapped JSObject produced this error:  * [Exception... 
"'Permission denied to get property UnnamedClass.classes' when calling method: 
[nsIAccessibleProvider::accessible]"  nsresult: "0x8057001e 
(NS_ERROR_XPC_JS_THREW_STRING)"  location: "<unknown>"  data: no]
The exception is happening at:

http://lxr.mozilla.org/seamonkey/source/accessible/src/base/
nsAccessibilityService.cpp#1846
This bug appears to be happening for all XUL child widgets of an application or 
dialog node run as a standalone.
The exception is the big clue.

Apparently we're running the chrome with the permissions of content, so it
doesn't have the security privileges necessary to create an accessible.

Similar to bug 241015. Probably the same fix.
Status: NEW → ASSIGNED
Assignee: aaronleventhal → pilgrim
Status: ASSIGNED → NEW
Assignee: pilgrim → nobody
Depends on: 241015
Summary: Node with application role does not always expose children → Windows opened with |Firefox -chrome myfile.xul| are not accessible
I'm sure it's a dupe of bug 241015. If it isn't please feel free to reopen bug.
Status: NEW → RESOLVED
Closed: 17 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.