Closed
Bug 851924
Opened 11 years ago
Closed 11 years ago
window.frames["foobar"] doesn't work in non-HTML documents
Categories
(Core :: DOM: Core & HTML, defect)
Core
DOM: Core & HTML
Tracking
()
RESOLVED
DUPLICATE
of bug 823227
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;
Updated•11 years ago
|
tracking-firefox22:
--- → ?
Keywords: regression
Summary: window.frames["foobar"] doesn't work → window.frames["foobar"] doesn't work in non-HTML documents
Comment 1•11 years ago
|
||
To be precise, it looks like it was this changeset specifically that regressed this: http://hg.mozilla.org/mozilla-central/rev/27d4aafb847d
Comment 2•11 years ago
|
||
(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
Comment 3•11 years ago
|
||
Fixing this in bug 823227.
Updated•11 years ago
|
You need to log in
before you can comment on or make changes to this bug.
Description
•