Closed
Bug 208975
Opened 23 years ago
Closed 22 years ago
Freezes in Preferences dialog when collapsing a developped tree view under some specific circumstances
Categories
(SeaMonkey :: Preferences, defect)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: christophe.bliard, Assigned: bugs)
Details
User-Agent: Mozilla/5.0 (X11; U; Linux i686; fr-FR; rv:1.3.1) Gecko/20030527 Debian/1.3.1-2
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; fr-FR; rv:1.3.1) Gecko/20030527 Debian/1.3.1-2
Mozilla simply freezes and you have to kill him
Reproducible: Always
Steps to Reproduce:
1.Open the Preferences dialog
2.Develop an entry of the Tree View on the right. Ensure the scrollbar is shown
after this action
3.Scroll down in the tree view
4.Select an element in the tree at the second level (a son of the developed entry)
5.Collapse the developed entry (the father of the selected entry). It must have
for consequence to hide the scrollbar, or it won't freeze
Actual Results:
The entry doesn'et collapse and it freezes
Expected Results:
collapse the tree
It seems to work with any developped entry, while the scrollbar is shown, while
the "collapse" action of an entry should hide the scrollbar and while the bar of
the scrollbar is not on the top of the scrollbar.
Sorry for my really bad english
Comment 1•22 years ago
|
||
Well, it works for me with 1.6 on Win2k and this is a fairly common task, so it
might be something special to your machine (nobody else has commented on this
bug in quite a while).
Could you please re-test it?
Does this happen with all tree elements? Does it happen with a clean profile?
| Reporter | ||
Comment 2•22 years ago
|
||
(In reply to comment #1)
> Well, it works for me with 1.6 on Win2k and this is a fairly common task, so it
> might be something special to your machine (nobody else has commented on this
> bug in quite a while).
> Could you please re-test it?
> Does this happen with all tree elements? Does it happen with a clean profile?
When I posted it, I tested it with my friend machines and the bug occured as
well. It was with Mozilla 1.3.1. Now I don't manage to reproduce it with Mozilla
1.6 so it must have been solved since.
Comment 3•22 years ago
|
||
Ok, thanks.
Resolving as WFM, but please reopen if this happens again.
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago
Resolution: --- → WORKSFORME
Updated•21 years ago
|
Product: Browser → Seamonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•