209987 - pages that contain <iframe ...> blah blah </iframe> fail to render

Status: RESOLVED INVALID

(SeaMonkey :: General, defect)

Description

[Daniel M. St.André]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4b) Gecko/20030507
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4b) Gecko/20030507

[[ The page that fails is a webmail server provided by our ICDsoft hosting vendor.]]
When I view pages that contain my mail, the formatted page presents the header
information, a message body area, and a footer.  The message body contains
<iframe src=show_body.php ...>
Some messages contain message body information properly displayed.  Other
messages have an empty body area.  All messages display the same when using Lynx
or IE 5.50.

Reproducible: Sometimes

Steps to Reproduce:
1.
2.
3.




I have view source page captures, but I don't know how to send them along with
this report.

Contact my administrative email address if you need a temporary mailbox for
testing purposes.  Trust me, I mean TEMPORARY.  Trust me, too, that heads will
roll if this gets abused in any way.  Unfortunately, I see no other way to
diagnose and debug this.

Comment 1

[Daniel M. St.André]

Attachment: view source page capture of a failing message

Comment 2

[Daniel M. St.André]

Comment on attachment 126048 [details]
view source page capture of a failing message

This attachment is the WRONG FILE.  I'll have to get another one.  Sorry.
I could not find a way to delete it so I marked this attachment "obsolete."

Comment 3

[Daniel M. St.André]

I keep trying to page capture without success.  I could use some guidance on how
to do that.

Comment 4

[Bill Mason]

*** Bug 209988 has been marked as a duplicate of this bug. ***

Comment 5

[Matthias Versen [:Matti]]

not compley Layout

Comment 6

[Boris Zbarsky [:bzbarsky]]

Daniel, could you save the failing message as "web page, complete", zip up the
relevant files, and attach to this bug?

Comment 7

[Vidar Haarr (not reading bugmail)]

Reporter: is this still a problem with a recent mozilla release/nightly? If it
is, could you please do what Boris suggested in the previous comment? Thanks!

Comment 8

[Michael Lefevre]

no response, so resolving as INVALID.

reporter (Daniel): if you can still reproduce this bug with a current version of
Mozilla, please reopen this bug, and attach the page causing the problem as
requested. thanks.