Closed Bug 648560 Opened 13 years ago Closed 6 years ago

contentWindow object enumeration fails

Categories

(Core :: XPConnect, defect)

2.0 Branch
x86
Windows 7
defect
Not set
normal

Tracking

()

RESOLVED INACTIVE

People

(Reporter: johnjbarton, Unassigned)

Details

Attachments

(2 files)

1. add the attached .html file to any extension content/ directory, eg firebug.
2. open chrome://theExtension/content/firebugWrapperexample.html
3. you should see an exception from line 11
Blake, Andreas, can you take a look at this please?
Component: DOM: Core & HTML → XPConnect
QA Contact: general → xpconnect
see also bug 649857
FYI, unlike bug 649857, this doesn't seem to work in 3.6.16 either. You get about the same error:
uncaught exception: [Exception... "Component is not available" nsresult: "0x80040111 (NS_ERROR_NOT_AVAILABLE)" location: "JS frame :: chrome://exampleext/content/firebugwrapperexample.fromjohn.html :: anonymous :: line 11" data: no]
I don't know what this bug is about. When I add the testcase here to a chrome mochitest, I don't get an exception on line 11 and everything seems to Just Work (TM). There are a couple of cases here where it seems like the testcase wants to use cwu instead of cw, but those cases work for me either way. Am I missing anything?
Attached patch testcase?Splinter Review
This is the testcase I created to try to test this bug.
Per policy at https://wiki.mozilla.org/Bug_Triage/Projects/Bug_Handling/Bug_Husbandry#Inactive_Bugs. If this bug is not an enhancement request or a bug not present in a supported release of Firefox, then it may be reopened.
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → INACTIVE
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: