Closed Bug 851924 Opened 12 years ago Closed 12 years ago

window.frames["foobar"] doesn't work in non-HTML documents

Categories

(Core :: DOM: Core & HTML, defect)

Product:
Core
Component:
DOM: Core & HTML
Type:
defect
Priority:
Not set
Severity:
major

Tracking

()

Status:
RESOLVED DUPLICATE of bug 823227
Tracking Flags:
Tracking Status
firefox22 - ---

People

(Reporter: philip.chee, Unassigned)

References

Details

(Keywords: regression)

window.frames["foobar"] doesn't work. STR: Start SeaMonkey. Open a MailNews window. Look at the Error Console output: Sun Mar 17 2013 23:32:45 Error: TypeError: window.frames.accountCentralPane is undefined Source file: chrome://messenger/content/tabmail.js Line: 893 Relevant code in tabmail.js: window.frames["accountCentralPane"].location.href = acctCentralPage;
tracking-firefox22: --- → ?
Keywords: regression
Summary: window.frames["foobar"] doesn't work → window.frames["foobar"] doesn't work in non-HTML documents
To be precise, it looks like it was this changeset specifically that regressed this: http://hg.mozilla.org/mozilla-central/rev/27d4aafb847d
(and this also affects Thunderbird to the point where we can't use it unless we work around this or fix it).
Severity: normal → major
Fixing this in bug 823227.
Status: NEW → RESOLVED
Closed: 12 years ago
tracking-firefox22: ? → -
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.