Tree widget continues to crash

VERIFIED INVALID

Status

()

Core
XUL
P3
blocker
VERIFIED INVALID
19 years ago
9 months ago

People

(Reporter: gayatrib, Assigned: David Hyatt)

Tracking

Trunk
x86
Windows NT
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

19 years ago
The tree widget is still crashing.
Here is a small test case:
--------------------------
<?xml version="1.0"?> <!-- -*- Mode: SGML; indent-tabs-mode: nil; -*- -->
<!--

  The contents of this file are subject to the Netscape Public License
  Version 1.0 (the "NPL"); you may not use this file except in
  compliance with the NPL.  You may obtain a copy of the NPL at
  http://www.mozilla.org/NPL/

  Software distributed under the NPL is distributed on an "AS IS" basis,
  WITHOUT WARRANTY OF ANY KIND, either express or implied. See the NPL
  for the specific language governing rights and limitations under the
  NPL.

  The Initial Developer of this code under the NPL is Netscape
  Communications Corporation.  Portions created by Netscape are
  Copyright (C) 1998 Netscape Communications Corporation.  All Rights
  Reserved.

-->

<?xml-stylesheet href="chrome://global/skin/xul.css" type="text/css"?>

<xul:window style="padding: 0px; width: 100%; height: 100%;"
	xmlns:html="http://www.w3.org/TR/REC-html40"
	xmlns="http://www.mozilla.org/keymaster/gatekeeper/there.is.only.xul"
class="dialog">


<html:div flex="100%">


	<tree id="tree" style="background-color: white; width: 100%; height:
100%; margin: 2px;">

		<treecol style="width: 25%"/>
		<treecol style="width: 70%"/>
		<treehead>
			<treerow>
				<treecell style="background-color: #CCCCCC;
border-right: 1px solid white;padding: 2px;">Migrate</treecell>
				<treecell style="background-color: #CCCCCC;
border-right: 1px solid white;padding: 2px;">User</treecell>
			</treerow>
		</treehead>

	</tree>


</xul:window>
----------------

Here is the stack trace:
NTDLL! 77f76148()
nsDebug::PreCondition(const char * 0x0125dea4, const char * 0x0125de8c, const
char * 0x0125de5c, int 1835) line 152 + 13 bytes
XULDocumentImpl::EndLoad(XULDocumentImpl * const 0x01ff2370) line 1835 + 50
bytes
XULContentSinkImpl::DidBuildModel(XULContentSinkImpl * const 0x01ff2e60, int 1)
line 546
CWellFormedDTD::DidBuildModel(CWellFormedDTD * const 0x01fc92e0, unsigned int 0,
int 1, nsIParser * 0x01ff05a0, nsIContentSink * 0x01ff2e60) line 285 + 20 bytes
nsParser::DidBuildModel(unsigned int 0) line 526 + 55 bytes
nsParser::ResumeParse(nsIDTD * 0x00000000, int 0) line 885
nsParser::OnDataAvailable(nsParser * const 0x01ff05a4, nsIURI * 0x01fec3b0,
nsIInputStream * 0x01ff2200, unsigned int 7786) line 1153 + 19 bytes
nsDocumentBindInfo::OnDataAvailable(nsDocumentBindInfo * const 0x01fec470,
nsIURI * 0x01fec3b0, nsIInputStream * 0x01ff2200, unsigned int 7786) line 2026 +
24 bytes
OnDataAvailableProxyEvent::HandleEvent(OnDataAvailableProxyEvent * const
0x01ff40e0) line 634
StreamListenerProxyEvent::HandlePLEvent(PLEvent * 0x01ff40e4) line 473 + 12
bytes
PL_HandleEvent(PLEvent * 0x01ff40e4) line 509 + 10 bytes
PL_ProcessPendingEvents(PLEventQueue * 0x00c85d20) line 470 + 9 bytes
_md_EventReceiverProc(HWND__ * 0x00650160, unsigned int 49393, unsigned int 0,
long 13131040) line 932 + 9 bytes
USER32! 77e713ed()
00c85d20()
---------------
(Assignee)

Updated

19 years ago
Status: NEW → RESOLVED
Last Resolved: 19 years ago
Resolution: --- → INVALID
(Assignee)

Comment 1

19 years ago
Your XUL is malformed.  You didn't close off your html:div tag.

Updated

19 years ago
Status: RESOLVED → VERIFIED

Comment 2

19 years ago
Marking Verified/Invalid

Comment 3

19 years ago
So, the proper response to malformed XUL is to crash then.
(Assignee)

Comment 4

19 years ago
It asserts.  It doesn't crash.

Comment 5

19 years ago
Sorry, took summary at face value.

Comment 6

18 years ago
BULK MOVE: Changing component from XUL to XP Toolkit/Widgets: XUL.  XUL 
component will be deleted.
Component: XUL → XP Toolkit/Widgets: XUL

Updated

9 years ago
Component: XP Toolkit/Widgets: XUL → XUL
QA Contact: ckritzer → xptoolkit.widgets
You need to log in before you can comment on or make changes to this bug.