Closed
Bug 8714
Opened 26 years ago
Closed 26 years ago
duplicate window ID causes infinite loop
Categories
(Core :: XUL, defect, P1)
Tracking
()
VERIFIED
FIXED
M15
People
(Reporter: alecf, Assigned: waterson)
References
Details
If you use an entity, with &entityName; and it's not defined in the document,
you get an ASSERT:
> Assertion: "must have content" (aContent) at file nsStyleSet.cpp, line 517
>
And then an infinite loop of some kind...sometimes I've seen it do a recursive
loop, other times not, but in anycase, the content does not draw, and the app is
basically locked up.
Chris -- I've checked this on NT and it works for me. Can you verify it on Win95
and Unix please?
Comment 2•26 years ago
|
||
With latest build (1999062810), I can't reproduce the problem described. Works
for me.
Updated•26 years ago
|
Assignee: petersen → rickg
Comment 3•26 years ago
|
||
With latest build (1999062810), I can't reproduce the problem described. Works
for me.
Reporter | ||
Comment 4•26 years ago
|
||
I just figured out the infinite loop problem - it happens when the <window> id
is the same as an id in the xul document.
So
<window (setup XUL namespaces, etc) id="abcd">
<titledbutton id="abcd"/>
</window>
will cause infinite recursion.
This might happen when ANY elements have the same ID, I'm not sure.
Peter -- this appears to be a XUL problem, not an entity problem. Please have
one of your guys take a gander.
Updated•26 years ago
|
Assignee: trudelle → hyatt
Priority: P3 → P1
Target Milestone: M8
Comment 6•26 years ago
|
||
assigning to hyatt as p1 for m8
Updated•26 years ago
|
Status: NEW → ASSIGNED
Component: Layout → XUL
Target Milestone: M8 → M10
Comment 7•26 years ago
|
||
cc'ing waterson. Moving to M10.
Updated•26 years ago
|
Target Milestone: M10 → M15
Assignee | ||
Updated•26 years ago
|
Assignee: hyatt → waterson
Status: ASSIGNED → NEW
Target Milestone: M15 → M10
Assignee | ||
Comment 8•26 years ago
|
||
Sorry, HYatt. This one is mine all mine.
Assignee | ||
Updated•26 years ago
|
Status: NEW → ASSIGNED
Assignee | ||
Updated•26 years ago
|
Summary: missing entities cause ASSERT, then infinite loop → duplicate window ID causes infinite loop
Assignee | ||
Updated•26 years ago
|
Target Milestone: M10 → M15
Assignee | ||
Comment 9•26 years ago
|
||
Uh, ok. I think the immediate rx for this is, "don't do that". Moving out to
M15.
Reporter | ||
Comment 10•26 years ago
|
||
but of course... eventually we gotta fix this though - this is also a denial of
service attack if content can hang the browser with content! :)
Assignee | ||
Updated•26 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 26 years ago
Resolution: --- → FIXED
Comment 11•26 years ago
|
||
Alec, could you please check to see if this problem has been fixed in the latest
build ? I'm not able to repo the problem.
Reporter | ||
Comment 12•26 years ago
|
||
I'll take your word for it.
this XUL would make it go into an infinite loop:
<window id="abcd">
<titledbutton id="abcd" value="hi there"/>
</window>
Updated•26 years ago
|
Status: RESOLVED → VERIFIED
Comment 13•26 years ago
|
||
I don't see this problem with the Oct 28th Linux build. Marking as verified
fixed.
Comment 14•26 years ago
|
||
I don't see this problem with the Oct 28th Linux build. Marking as verified
fixed.
Comment 15•25 years ago
|
||
BULK MOVE: Changing component from XUL to XP Toolkit/Widgets: XUL. XUL
component will be deleted.
Component: XUL → XP Toolkit/Widgets: XUL
Component: XP Toolkit/Widgets: XUL → XUL
QA Contact: chrispetersen → xptoolkit.widgets
You need to log in
before you can comment on or make changes to this bug.
Description
•