Closed Bug 336756 Opened 18 years ago Closed 17 years ago

turn warning on frame construction within reflow back into an assertion

Categories

(Core :: Layout, defect)

Product:
Core
Component:
Layout
Type:
defect
Priority:
Not set
Severity:
critical

Tracking

()

Status:
RESOLVED FIXED

People

(Reporter: dbaron, Unassigned)

References

Details

(Whiteboard: [sg:want P4]) 

I changed another one of the assertions from bug 310985 into a warning because it fires too much; this is a bug on changing it back.
Flags: blocking1.9?
Whiteboard: [wanted-1.9]
Whiteboard: [wanted-1.9] → [wanted-1.9][sg:want P4]
This bug only has one dependency, which was recently fixed.  Is it time to turn this warning back into an assertion?
I was planning to, but from the tinderbox log it looks like it's not really fixed.  I was going to try looking into it later today...
Er, it's the other one that's still showing up; this one may be fixed.  But I haven't seen it for a while anyway.
"The other one" being bug 334460, I'm guessing?
Yep, I went through the whole thunderbird options dialog and couldn't get the assertion to fire, so I flipped this one back to an assertion.
Status: NEW → RESOLVED
Closed: 17 years ago
Resolution: --- → FIXED
Flags: in-testsuite-
Flags: wanted1.9+
Whiteboard: [wanted-1.9][sg:want P4] → [sg:want P4]
Product: Core → Core Graveyard
Component: Layout: Misc Code → Layout
Product: Core Graveyard → Core
You need to log in before you can comment on or make changes to this bug.