On Sun, 2005-02-27 at 12:45 -0600, Boris Zbarsky wrote:
> Tom Copeland wrote:
> > I'm getting a "ASSERTION: How'd we get a floated inline frame?" message
> > from a small embedded Mozilla program...
> 
> What webpage are you loading when you get this assert?  Do you get the same 
> assert in a debug Mozilla on the same page (I would hope that you do...).

By the way, I also rebuilt Mozilla 1.7.3 with debug, and the same thing
occurred in the same place:

===============================
nsPluginNativeWindowGtk2: NPPVpluginNeedsXEmbed=0
nsPluginNativeWindowGtk2: call SetWindow with xid=0x2a00052
###!!! ASSERTION: How'd we get a floated inline frame? The frame ctor
should've dealt with this.: 'aReflowState.mStyleDisplay->mFloats ==
NS_STYLE_FLOAT_NONE', file nsLineLayout.cpp, line 1318
Break: at file nsLineLayout.cpp, line 1318
===============================

Line 1318 + context:

===============================
  NS_PRECONDITION(pfd && pfd->mFrame, "bad args, null pointers for frame
data");
  // Compute right margin to use
  if (0 != pfd->mBounds.width) {
    NS_ASSERTION(aReflowState.mStyleDisplay->mFloats ==
NS_STYLE_FLOAT_NONE,
                 "How'd we get a floated inline frame? "
                 "The frame ctor should've dealt with this.");
===============================

Hm.  pfd->mBounds.width... let me poke around to see what's going on
there...

Thanks for the help,

Yours,

Tom


_______________________________________________
mozilla-embedding mailing list
[email protected]
http://mail.mozilla.org/listinfo/mozilla-embedding

Reply via email to