611686 - Eliminate WARNING spew from nsCSSFrameConstructor

Status: RESOLVED FIXED

(Core :: Layout, defect, P4)

Comment 1

[David Baron :dbaron: (⌚️UTC-4, no longer working on Mozilla)]

I assume you mean:

WARNING: Positioned frame that does not handle positioned kids; looking further up the parent chain: file .../layout/base/nsCSSFrameConstructor.cpp, line 5565


Possible duplicate of bug 299315.

Comment 2

[David Baron :dbaron: (⌚️UTC-4, no longer working on Mozilla)]

For the record, this is basically a warning saying "we haven't fixed bug 455338 yet"; we should probably ditch the warning.  Though it's a little scary that we hit it on startup, since that means there's something that depends on that bug in our chrome or start page.

Comment 3

[David Baron :dbaron: (⌚️UTC-4, no longer working on Mozilla)]

Attachment: remove warning

Comment 4

[Boris Zbarsky [:bzbarsky]]

Fwiw, we hit this warning any time we enter ContentRangeInserted with a XUL parentFrame that's rel-pos, even if there's nothing abs pos inside, since constructing the frame constructor state looks up the absolute containing block.

For browser.xul there's a rel pos button box frame that has kids dynamically inserted.

Comment 5

[Boris Zbarsky [:bzbarsky]]

Comment on attachment 490134 [details] [diff] [review]
remove warning

r=me

Comment 6

[David Baron :dbaron: (⌚️UTC-4, no longer working on Mozilla)]

http://hg.mozilla.org/mozilla-central/rev/0b5df68704ad