97177 - Embedding navigator.xul in an IFrame breaks setOverLink()

Status: NEW

(SeaMonkey :: UI Design, defect)

Description

[Colin Phillips]

If you embed the file navigator.xul into an iframe within a XUL <window>, the
function setOverLink() is never called.  "setOverLink()" is a function of
nsBrowserStatusHandler in navigator/content/nsBrowserStatusHandler.js.  If the
navigator.xul file is in it's own window, everything works fine, but if you
setup a file with the following, the function setOverLink is never called:
<window>
   <iframe src="chrome://navigator/content/navigator.xul"/>
</window>
This functionality is needed by OEone.

Comment 1

[Paul Chen]

reassigning to hyatt since he can probably figure out what the problem is faster
than anyone else

Comment 2

[David Hyatt]

Add type="content" to your iframe.

<iframe type="content" ... />

Comment 3

[Colin Phillips]

Unfortunately that does not do the trick.

I get the following error when trying to set type="content"

Error: uncaught exception: [Exception... "Component returned failure code:
0x80004005 (NS_ERROR_FAILURE) [nsIWebNavigation.sessionHistory]"  nsresult:
"0x80004005 (NS_ERROR_FAILURE)"  location: "JS frame ::
chrome://navigator/content/navigator.js :: Startup :: line 377"  data: no]

where line 377 is:
// wire up session history before any possible progress notifications for
back/forward button updating
webNavigation.sessionHistory =
Components.classes["@mozilla.org/browser/shistory;1"].createInstance(Components.interfaces.nsISHistory);

Comment 4

[David Hyatt]

Our XUL isn't designed to work in iframes.  Suggest you edit the XUL to work
around your problem.

Comment 5

[Peter Bojanic]

Nominating for mozilla1.0. Asking ColinP to comment on the relative importance
of this one for Penzilla, in the grand scheme of things.

Comment 6

[Colin Phillips]

We have a work arund within Penzilla which accomplishes this same thing for us.
 I don't know if this is really a bug given what Hyatt said about iframes.

Comment 7

[Tony Mechelynck [:tonymec]]

- No comments in more than 6 years.

- I don't understand what this bug is about. Is it about something that still happens and is felt like in need of a fix?

- Is this bug a SeaMonkey bug or should it move to somewhere else (Core? Toolkit? Other apps? ...)

Comment 8

[Colin Phillips]

As the originator of the bug, we're no longer in need of it (the company doesn't use this technology any more).  So it's really up to you to decide whether or not this is something of value to fix.

Comment 9

[Tony Mechelynck [:tonymec]]

(In reply to comment #8)
> As the originator of the bug, we're no longer in need of it (the company
> doesn't use this technology any more).  So it's really up to you to decide
> whether or not this is something of value to fix.
> 

So the reporter isn't anymore interested in fixing the bug. Anyone else? Unless someone speaks up within a week or so, I move this bug be resolved WONTFIX.

Comment 10

[Tony Mechelynck [:tonymec]]

Resetting A+QA on bug where apparently no advance towards solving it happened since 2001 or maybe earlier. David, if you still want it, go ahead. Otherwise, my comment #9 stands except I don't have the power to set a WONTFIX.