8715 - FrameInner(iframe) didn't set max-element-size!

Status: VERIFIED WORKSFORME

(Core :: Layout, defect, P3)

Description

[Akkana Peck]

Starting up the editor (apprunner -edit) on linux or windows, I always get a
slew of messages to stdout:

nsContainerFrame: FrameInner(iframe)(1)@0x82af3c8 didn't set max-element-size!
nsContainerFrame: FrameInner(iframe)(1)@0x82af3c8 didn't set max-element-size!
Note: verifyreflow is disabled
nsContainerFrame: FrameInner(iframe)(1)@0x82af3c8 didn't set max-element-size!
nsContainerFrame: FrameInner(iframe)(1)@0x82af3c8 didn't set max-element-size!
nsContainerFrame: FrameInner(iframe)(1)@0x82af3c8 didn't set max-element-size!
nsContainerFrame: FrameInner(iframe)(1)@0x82af3c8 didn't set max-element-size!
nsContainerFrame: FrameInner(iframe)(1)@0x82af3c8 didn't set max-element-size!
nsContainerFrame: FrameInner(iframe)(1)@0x82af3c8 didn't set max-element-size!
[ ... ]
nsContainerFrame: FrameInner(iframe)(1)@0x82af3c8 didn't set max-element-size!

Steve says:
> this is a bug in iframe.  it would occur if the iframe were in
> a table cell's contents.

Comment 1

[rickg]

An easy kill of this layout bug for you.

Comment 2

[Nisheeth Ranjan]

I tried this on a July 9th NT debug build and did not see these messages.  I'm
updating to the tip to see if this problem still exists...

Comment 3

[Nisheeth Ranjan]

We no longer get these error messages in the tip debug build on NT.  I checked
that the printf that outputs these messages is enabled for the debug build.

Steve and Akkana, if you are ok with it, I'm going to mark this bug worksforme.
Also ccing Eric Pollmann and Chris Karnaze to see if they checked in a fix that
could have fixed this problem.

Comment 4

[Akkana Peck]

I agree, I no longer see these messages.  Someone obviously checked in a fix
which cures the problem.

Comment 5

[Nisheeth Ranjan]

Marking bug worksforme.

Comment 6

[Chris Petersen]

Since I can't reproduce either, marking as verified works for me.