Closed
Bug 102150
Opened 24 years ago
Closed 24 years ago
XUL in XHTML: <tree> in XHTML file causes crash
Categories
(Core :: Layout, defect)
Tracking
()
RESOLVED
INVALID
Future
People
(Reporter: shawn1, Assigned: hyatt)
Details
(Keywords: crash, testcase)
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.4) Gecko/20010913
BuildID: 2001091303
A tree control that works properly in a XUL source file causes Mozilla to crash
when contained within an XHTML file.
Reproducible: Always
Steps to Reproduce:
1. create a XUL file containing a tree. load it, watch it work
2. copy the XUL file to an .xhtml file, edit the header/footer to make valid XHTML.
3. try loading this XHTML file, observe the crash.
Actual Results: Crash
Expected Results: I presume that XUL controls should render when embedded in
XHTML files (most controls do)
I include simple test files that reproduce the problem on my browser.
The first works as expected, the second crashes.
Working XUL case (errorcaseGood.xul):
<box xmlns="http://www.mozilla.org/keymaster/gatekeeper/there.is.only.xul"
xmlns:h="http://www.w3.org/1999/xhtml">
<tree>
<treechildren>
<treeitem>
<treerow>
<treecell label="I ate a half-dozen hot dogs"/>
</treerow>
</treeitem>
</treechildren>
</tree>
</box>
Crashing XHTML case (errorcaseBad.xhtml):
<h:html xmlns="http://www.mozilla.org/keymaster/gatekeeper/there.is.only.xul"
xmlns:h="http://www.w3.org/1999/xhtml">
<h:head/>
<h:body>
<tree>
<treechildren>
<treeitem>
<treerow>
<treecell label="I ate a half-dozen hot dogs"/>
</treerow>
</treeitem>
</treechildren>
</tree>
</h:body>
</h:html>
Comment 1•24 years ago
|
||
Confirmed with build 2001-09-26-03 (trunk) on Windows 98 SE.
Talkback IDs: TB36004526M and TB36004727Y
| Assignee | ||
Updated•24 years ago
|
Status: NEW → ASSIGNED
Target Milestone: --- → Future
Comment 3•24 years ago
|
||
Testcase no longer crashes.
This bug should probably be closed.
Comment 4•24 years ago
|
||
the olde tree layout code is no more
Status: ASSIGNED → RESOLVED
Closed: 24 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•