7745 - IFRAMES and JavaScript

Status: VERIFIED FIXED

Description

[bmurtha]

Hello,

   I'm really bummed, I used to work for LookSmart and we had a hellva' time trying to find a way to use javascript and iframes so that we could display the same page dynamic content to the client. This took months of debugging and coding, and when I opened and saw it broke again, I almost cried. Is their anyway you guys could engineer some backwards compatiblity. I mean, I think it's great that you guys are supporting I frames. They will make like much easier for everyone. And maybe for this type of work we should have used a browser detect. I just wanted you guys to know my pain. Which really don't matter, I don't work for that company anymore and so it's someone else's problem. But I did just want to share this with you.

P.S.

 Aside from this, you guys are kickin' ass with this thing. I was a Netscape person, gone IE, but seriously thinking of changing camps again. It all boils down to who makes a better browser. And from what I can see, you guys are winning.

Regards,

Bryan

Comment 1

[leger]

Updating QA contact and component.  (Please do not use Javacript.  Let's try
Layout guys, and if this is indeed a Javascipt issue, assigne to Javascript
Engine)

Comment 2

[rickg]

Vidur -- can you make sense of this?

Comment 3

[vidur (gone)]

The main layout issue on this page is that the block contents of the <IFRAME>s
are being pushed out of the IFRAME. In reality, the should be children of the
IFRAME (and the layout code doesn't render them).

I'm attaching a reduced test case and a proposed patch. Note that this should be
reasonable similar to what we do for APPLETs, EMBEDs and OBJECTs, right?

There is another problem with the ILAYER/IFRAME below the hrule. The source of
the IFRAME is a https: URL that we can't seem to load (Note that Navigator 4.0
can't seem to load it either, though it loads the ILAYER URL without a problem.
Is the server doing some sort of sniffing?).

Comment 4

[vidur (gone)]

Oops. Navigator did load the IFRAME URL - it just took a long time.

Comment 5

[vidur (gone)]

Created attachment 441 [details]
reduced test case for content inside IFRAME

Comment 6

[vidur (gone)]

Created attachment 442 [details] [diff] [review]
Proposed patch

Comment 7

[harishd]

Per spec. IFRAME can contain "flow" elements.  Thanx vidur.
The fix is in.

Marking bug fixed.

Comment 8

[Chris Petersen]

Fixed in the July 16th Build (All platforms: Mac, Windows, and Linux)