Closed
Bug 177202
Opened 23 years ago
Closed 23 years ago
Loading a directory in navigator causes lag and occasional crash?
Categories
(Camino Graveyard :: OS Integration, defect)
Tracking
(Not tracked)
VERIFIED
FIXED
People
(Reporter: jtrin, Assigned: sfraser_bugs)
References
()
Details
In Build ID: 2002102804, loading a directory filled with (in this case images)
locally causes chimera to hand (look like it's still loading). I did this with
a folder of jpegs by dropping a jpeg on chimera and truncating the name to load
the folder (I wanted to see the changes in this build). The list came up, but
the folder seemed to still be loading. After a minute I clicked on and image
link, looked at the image and clicked back and chimera crashed. I'm not seeing
icons and the folders take forever to load. Also...shouldn't we be able to drag
and drop a folder onto the icon or url bar instead of just a file and truncating
the name or typing in the name manually?
|
Assignee | |
Comment 1•23 years ago
|
||
This was fixed today.
Status: UNCONFIRMED → RESOLVED
Closed: 23 years ago
Resolution: --- → FIXED
|
Reporter | |
Comment 3•22 years ago
|
||
Question: when I downloaded 2002102804 the release notes said icons or something
had been patched for directories, but the build still had that bug. Simon, your
post is dated 1028, but you didn't mention what build you were reporting
against. Is my original post unclear, were we working with different builds, or
did nobody manage to replicate this bug. If it wasn't fixed in my 1028 build or
after then it's not a regression. If someone just verified it in 2002111204
(albeit under 10.2.2) shouldn't it be reopened instead of verified fixed and not
tracked under the meta system unless someone tested it as resolved? Possible
this wasn't ever fixed?...unless someone couldn't reproduce it? I wouldn't say
crashing the browser is minor.
-j
|
|
Assignee | |
Comment 4•22 years ago
|
||
If I made the 'fixed' comment on 10/28, the first build with the fix will be 10/29.
Anyway, if this is verified fixed in a more recent build, what's the problem?
|
|
Reporter | |
Comment 5•22 years ago
|
||
Sorry simon, I wasn't clear on if it was verified as a bug or verified fixed.I
thought it may have been changed to verified fixed in october. Is there a way to
see history of the (verified fixed/reopen bug/mark as closed) selections?
thanks -j
You need to log in
before you can comment on or make changes to this bug.
Description
•