Closed
Bug 81205
Opened 23 years ago
Closed 15 years ago
loading mailnews into an iframe
Categories
(SeaMonkey :: MailNews: Message Display, defect)
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: danp, Unassigned)
Details
Attachments
(3 files)
I have successfully loaded mailnews into an iframe but it wasn't without its
difficulties. It seems as though any reference to top within an iframe does not
point to its intended location in the DOM. What I did to solve this problem was
in the messenger.xul file I made a single global variable as follows:
<script type="application/x-javascript">
var top = self;
</script>
I zipped up the messenger.jar file and everything worked nicely. I also started
up mailnews in a normal fashion and it seemed to function properly. This leads
me to believe that all references to top could possibly be safely changed to
self in order to make it very easy to place mailnews into an iframe.
Updated•23 years ago
|
Severity: normal → enhancement
Status: UNCONFIRMED → NEW
Ever confirmed: true
Comment 1•23 years ago
|
||
yes, this is what hyatt recommended as well. Not an enhancement.
Severity: enhancement → normal
Reporter | ||
Comment 2•23 years ago
|
||
There are other issues with this bug now that really block me from using
mail/news in an iframe. I need mail/news to load into an iframe in a window
that also contains a browser. What seems to be happening is that when mail/news
loads into an iframe everything works quite nicely but when switching back to a
browser in the same window a lot of the javascript functionality seems hampered.
This appears to be some type of javascript sandbox that limits the
functionality of javascript in a window that mail/news is loaded into (perhaps
this is incorrect thinking though).
Everything seems to boil down to SetDOMWindow and the error code we're told
about is NS_BINDING_ABORT which according to shaver is "...somewhat unfortunate,
because it's probably removed from the original error condition."
Severity: normal → blocker
Reporter | ||
Comment 3•23 years ago
|
||
Reporter | ||
Comment 4•23 years ago
|
||
Reporter | ||
Comment 5•23 years ago
|
||
Reporter | ||
Comment 6•23 years ago
|
||
Here's a test case for my problem, using a 0.9.2 browser:
1. replace your chrome/all-packages.rdf with the one I'm sending
2. place the test.xul file in the mozilla root dir (i.e. wherever you installed
mozilla to)
3. replace you chrome/messenger.jar with the one provided (I had to modify
messenger.xul and globally set top = self, as was described in the bug)
4. open a terminal and launch mozilla using the following command
/path/to/mozilla/mozilla -chrome chrome://spdwtest/content/test.xul
5. Now launch a messenger instance by clicking the messenger button
6. View a message
7. Launch a browser instance
8. go to http://developer.netscape.com/docs/index.html?cp=dev01tdoc
9. watch as things start to freeze, you can scroll with the mouse wheel but the
scroll bars will stop responding and you can't click on any links in the page.
Reporter | ||
Comment 7•23 years ago
|
||
I've noticed something with the recommended nightly build from mozillazine
(2001-09-24-08) has the new browser tabbing widget. Messenger appears to be
loadable into this widget as opposed to the iframe and the other tabs that are
loaded seem to be unaffected. Seems there is some magic in the browser tabbing
widget.
Comment 8•23 years ago
|
||
Nominating for mozilla 1.0. We've had an inelegant hack in Penzilla for the last
year to work around this bug.
Whiteboard: mozilla.10
Comment 9•23 years ago
|
||
Erroneously added the the mozilla1.0 keyword to the status whiteboard instead of
the keywords field.
Keywords: mozilla1.0
Whiteboard: mozilla.10
Comment 11•20 years ago
|
||
See http://www.theregister.co.uk/2004/07/30/email_privacy/ regarding the serious
danger of iFRAMES
Updated•20 years ago
|
Product: Browser → Seamonkey
Updated•20 years ago
|
Assignee: sspitzer → mail
Updated•16 years ago
|
Assignee: mail → nobody
QA Contact: esther → message-display
Comment 12•15 years ago
|
||
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.
If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.
Query tag for this change: mass-UNCONFIRM-20090614
Status: NEW → UNCONFIRMED
Comment 13•15 years ago
|
||
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.
If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.
Query tag for this change: mass-UNCONFIRM-20090614
Comment 14•15 years ago
|
||
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.
If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.
Query tag for this change: mass-UNCONFIRM-20090614
Comment 15•15 years ago
|
||
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.
If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.
Query tag for this change: mass-UNCONFIRM-20090614
Comment 16•15 years ago
|
||
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.
If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.
Query tag for this change: mass-UNCONFIRM-20090614
Comment 17•15 years ago
|
||
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.
If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.
Query tag for this change: mass-UNCONFIRM-20090614
Comment 18•15 years ago
|
||
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.
If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.
Query tag for this change: mass-UNCONFIRM-20090614
Comment 19•15 years ago
|
||
MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but still has no comment since the inception of the SeaMonkey project 5 years ago.
Because of this, we're resolving the bug as EXPIRED.
If you still can reproduce the bug on SeaMonkey 2 or otherwise think it's still valid, please REOPEN it and if it is a platform or toolkit issue, move it to the according component.
Query tag for this change: EXPIRED-20100420
Status: UNCONFIRMED → RESOLVED
Closed: 15 years ago
Resolution: --- → EXPIRED
You need to log in
before you can comment on or make changes to this bug.
Description
•