Closed Bug 113810 Opened 23 years ago Closed 23 years ago

nsFramemanager.cpp warnings make the layout regression tests a real pain

Categories

(Core :: Layout, defect)

x86
All
defect
Not set
normal

Tracking

()

RESOLVED FIXED

People

(Reporter: bernd_mozilla, Assigned: dbaron)

References

()

Details

Attachments

(1 file)

37.33 KB, text/plain
Details
David, your checking for bug 110911 has caused a regression. I cant load any page without a bunch of warnings:"already have a primary frame for content". Tinderbox shows the same under linux.
They're just WARNINGs, i.e., things that print on the console. They shouldn't bring up dialogs or anything, and they are something that should be investigated, which is why I put them in.
How do they make the regression tests a pain?
Attached file logfile
I think that logfile looks somehow cluttered.
Index: nsFrameManager.cpp =================================================================== RCS file: /cvsroot/mozilla/layout/html/base/src/nsFrameManager.cpp,v retrieving revision 1.94 diff -u -d -r1.94 nsFrameManager.cpp --- nsFrameManager.cpp 6 Dec 2001 05:45:01 -0000 1.94 +++ nsFrameManager.cpp 6 Dec 2001 19:51:19 -0000 @@ -694,7 +694,7 @@ // Add a mapping to the hash table PrimaryFrameMapEntry *entry = NS_STATIC_CAST(PrimaryFrameMapEntry*, PL_DHashTableOperate(&mPrimaryFrameMap, aContent, PL_DHASH_ADD)); -#ifdef DEBUG +#ifdef DEBUG_dbaron if (entry->frame) { NS_WARNING("already have primary frame for content"); }
Fixed. Now only I will see warnings about how messed up our frame construction code is.
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: