Closed
Bug 22250
Opened 26 years ago
Closed 26 years ago
Reproducable Mozilla crash when clicking on a directory
Categories
(SeaMonkey :: General, defect, P1)
Tracking
(Not tracked)
VERIFIED
FIXED
M13
People
(Reporter: dejong, Assigned: hyatt)
Details
I got this crash on my RedHat 5.2 system. This was from the CVS Dec 20th.
Make these directories.
mkdir /tmp/test
touch /tmp/test/f1
touch /tmp/test/f2
mkdir /tmp/test/one
mkdir /tmp/test/one/onesub
touch /tmp/test/one/onesub/f1
touch /tmp/test/one/onesub/f2
mkdir /tmp/test/two
mkdir /tmp/test/two/twosub
touch /tmp/test/two/twosub/f1
touch /tmp/test/two/twosub/f2
Now type file:///tmp/test into the browser window. This should open up the
root window and display the files and directories like this.
--------
f1
f2
> one
> two
--------
Now click on the > to the left of the directory "one"
to expand the contents of the directory.
After doing that the following should be displayed.
--------
f1
f2
\/ one
> onesub
> two
--------
Now click on the > to the left of the directory "onesub"
to expand the contents of the directory.
After doing that the contents of onesub should be displayed
but the browser seems to close the "onesub" and "one" directories
in the tree. The incorrect listing looks like this.
--------
f1
f2
\/ one
> two
--------
You can now crash mozilla by clicking on the \/ widget to the
left of the "one" directory.
The crash seems to be happinging in seemingly random locations.
I have reproduced this error a number of times and the crash
does not seem to happend in the same place twice.
Updated•26 years ago
|
Severity: normal → critical
Updated•26 years ago
|
Assignee: nobody → trudelle
QA Contact: nobody → claudius
Comment 1•26 years ago
|
||
I'm going to guess that this may be a problem with the widget itself, and sending
the bug over to trudelle for consideration.
dejong, thanks for the beautiful bug report!
Updated•26 years ago
|
Assignee: trudelle → hyatt
Priority: P3 → P1
Target Milestone: M13
Comment 2•26 years ago
|
||
assigning to hyatt as p1 for m13
| Assignee | ||
Updated•26 years ago
|
Status: NEW → ASSIGNED
| Assignee | ||
Comment 3•26 years ago
|
||
This seems to be the same as the insidious bug in CalculateRowHeights.
Is this actually still happening, or are you using older bits?
| Assignee | ||
Updated•26 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 26 years ago
Resolution: --- → FIXED
| Assignee | ||
Comment 4•26 years ago
|
||
No comment given. I'm assuming this is a dup of the problem I fixed. Closing
out.
Hi all.
This is a ammendment to the original bug report. The crashing problem
was fixed, but there is another problem that seems to be directly related.
If I should open another bug for this problem please tell me.
When a directory name is double clicked, it will not display the
file contents until the actual > widget is clicked to expand the
entry. This is not the correct thing to do.
1. type file:///tmp/test into the browser window. This should open
up the root window and display the files and directories like this.
--------
f1
f2
> one
> two
--------
Now double click on the directory "one" (NOT the > widget to
the left of the text "one"). You should see the following
result.
--------
f1
f2
\/ one
> two
--------
Double click "one" again to return it to the original state.
Now click on the > widget to the left of the text "one".
The following should be displayed.
--------
f1
f2
\/ one
> onesub
> two
--------
Click on the > widget to return it to the original state.
Now if you double click on the text "one", it will open
the directory just like a click on the > widget. The
bug here is that a double click on the text should have
displayed the contents of the subdirectory, it does not.
I should not have to click on the > widget to get a
double click on the text "one" to work.
Comment 6•26 years ago
|
||
dejong, what you describe needs to be it's own seperate bug. I would cut and paste what
you already wrote into a new bug - including the info on setting up the test directories. I
believe the component for the new bug would be xptoolkit.
Ok, I opened up a new bug for the second "double click" problem. I am going
to mark this bug as verified because I checked it and it seems to work
just fine. The new bug number is 23654 in case anyone wanted to know.
Updated•21 years ago
|
Product: Browser → Seamonkey
| Comment hidden (collapsed) |
You need to log in
before you can comment on or make changes to this bug.
Description
•