Closed Bug 445263 Opened 17 years ago Closed 17 years ago

iframed content never finishes loading in Camino.

Categories

(Camino Graveyard :: General, defect)

PowerPC
macOS
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 385676

People

(Reporter: bugzilla, Unassigned)

References

()

Details

User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en; rv:1.8.1.14) Gecko/20080512 Camino/1.6.1 (like Firefox/2.0.0.14) Build Identifier: Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en; rv:1.8.1.14) Gecko/20080512 Camino/1.6.1 (like Firefox/2.0.0.14) Using iframe to embed a (flash?) gallery from dotMac mobileMe results in perpetual "loading" when browsed via Camino. Other browsers, including FireFox, work fine. See ben-amotz.com, which contains the following iframe: <iframe height="100%" allowTransparency="true" frameborder="0" scrolling="yes" style="width:100%;border:none" src="http://gallery.me.com/benamotz#gallery"></iframe> The problem persists with a simple iframe that only specifies the src. Reproducible: Always Steps to Reproduce: 1.Open Camino 2. Visit ben-amotz.com 3. Watch the "loading" message continue forever Actual Results: The "loading" message persists without end Expected Results: Expected to see content from: http://gallery.me.com/benamotz#gallery
With a trunk build, I don't see the described behaviour at all; the only thing I can ever get to happen is the "unsupported browser" message (even if I check the "don't show again" box and click "use current browser"). That's certainly TE-worthy, but as I noted, it's not the described bug...
With both Camino 1.6.2rc and Fx 2.0.0.16, I get the same issue: perpetual 'loading' for the iframe. Error console flags me this: [JavaScript Error: "uncaught exception: Permission denied to call method Location.toString"] This may very well be a dupe of bug 385676. Camino 2.0a1pre loads the page just fine here.
(In reply to comment #2) > This may very well be a dupe of bug 385676. Yeah, it sure sounds like it, and I think that makes it WORKSFORME, since this is unlikely to be fixed on branch from what I can tell.
Status: UNCONFIRMED → RESOLVED
Closed: 17 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.