Closed
Bug 22107
Opened 25 years ago
Closed 25 years ago
[CRASHER] absolutely position xul box crashes mozilla
Categories
(Core :: XUL, defect, P2)
Tracking
()
RESOLVED
FIXED
M14
People
(Reporter: rginda, Assigned: eric)
References
Details
(Keywords: crash, Whiteboard: didn't make box landing will check in soon)
Attachments
(1 file)
|
258 bytes,
text/plain
|
Details |
loading the attached testcase in apprunner (save it to a xul file first)
results in:
###!!! ASSERTION: nsBox::ERROR!! Box info list count does not match frame
count!!: 'length == mCount', file nsBoxFrame.cpp, line 2554
###!!! Break: at file nsBoxFrame.cpp, line 2554
###!!! ASSERTION: nsBox::ERROR!! box info list and child info lists don't
match!!!: 'info->frame == child', file nsBoxFrame.cpp, line 2564
###!!! Break: at file nsBoxFrame.cpp, line 2564
###!!! ASSERTION: nsBox::ERROR!! box info list and child info lists don't
match!!!: 'info->frame == child', file nsBoxFrame.cpp, line 2564
###!!! Break: at file nsBoxFrame.cpp, line 2564
[rginda@rg2 bin]$
|
Reporter | |
Comment 1•25 years ago
|
||
|
||
Comment 2•25 years ago
|
||
adding alecf to the cc list.
|
|
Reporter | |
Comment 3•25 years ago
|
||
The attached testcase doesn't reproduce the problem... I'll work up one that
does.
|
|
Reporter | |
Comment 4•25 years ago
|
||
I was wrong about being wrong. It looked like I was running the wrong file
when in fact I wasn't.
The previous testcase DOES in fact reproduce the failure for me.
|
||
Updated•25 years ago
|
Assignee: trudelle → evaughan
Severity: normal → critical
OS: Linux → All
Priority: P3 → P2
Target Milestone: M13
|
|
||
Comment 5•25 years ago
|
||
reproduced using 12/17 opt comm bits on Win98,setting OS all, severity critical
Why do we have [CRASHER] in the summary? Isn't the existing 'crash' sufficient?
Does't critical severity indicate the same thing? All these tags are crowding
out the bug summaries!
assigning to evaughan as p2 for M13
|
Assignee | |
Updated•25 years ago
|
Status: NEW → ASSIGNED
Target Milestone: M13 → M14
|
|
Assignee | |
Comment 7•25 years ago
|
||
Absolute positioning only works in html not in xul. Of course it should not
crash when you do so. So this is not a blocker. Moving to m14.
BULK MOVE: Changing component from XUL to XP Toolkit/Widgets: XUL. XUL
component will be deleted.
Component: XUL → XP Toolkit/Widgets: XUL
|
|
Assignee | |
Updated•25 years ago
|
Whiteboard: have a fix will check into m14 when it opens
|
|
||
Comment 9•25 years ago
|
||
putting on beta1 radar
|
|
Assignee | |
Updated•25 years ago
|
Whiteboard: have a fix will check into m14 when it opens → This is fixed awaiting dirty box landing
|
|
Assignee | |
Updated•25 years ago
|
Whiteboard: This is fixed awaiting dirty box landing → didn't make box landing will check in soon
|
|
Assignee | |
Comment 11•25 years ago
|
||
fixed.
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
|
||
Comment 12•25 years ago
|
||
please ignore, massive spam giving jrgm@netscape.com backlog of XPToolkits
resolved fixed bugs to verify
QA Contact: paulmac → jrgm
Component: XP Toolkit/Widgets: XUL → XUL
QA Contact: jrgmorrison → xptoolkit.widgets
You need to log in
before you can comment on or make changes to this bug.
Description
•