Closed Bug 271989 Opened 20 years ago Closed 17 years ago

Userlist changes (joins/parts/ops) lose selection and scroll position

Categories

(Other Applications :: ChatZilla, defect)

defect
Not set
minor

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: aurelthebest, Assigned: rginda)

References

Details

(Whiteboard: [cz-0.9.80])

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; fr-FR; rv:1.7.5) Gecko/20041108 Firefox/1.0 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; fr-FR; rv:1.7.5) Gecko/20041108 Firefox/1.0 When I select a nick name in the left pane of a channel, the refresh makes the cursor returns to the top of the list. So it's difficult (almost impossible) to select somebody which is situated in a long list of connected people. Reproducible: Always Steps to Reproduce: Connecting to a channel with a lot of people (like wanadoo.fr) and go down the list in order to select and to talk to someone who is situated near the end of the list. Actual Results: When the refresh is carried out, the cursor returns to the top of the list and the nick name is no more selected. Expected Results: remind the nickname selected or the cursor position in the list
I think this is a fair bug, though I don't know how fixable it is. Can someone confirm this bug?
What is the "refresh"?
I just observed it nuking the select/scroll position when someone joined, so that is definately one place. I suspect anywhere we do that RDF tree root change thingy it is likely to happen.
Status: UNCONFIRMED → NEW
Ever confirmed: true
OS: Windows XP → All
Hardware: PC → All
Depends on: 307923
Depends on: 325358
Depends on: 315913
Summary: refresh of connected people'list on a channel lose the contact i've selected and return to the top of the list → Userlist changes (joins/parts/ops) lose selection and scroll position
Version: unspecified → Trunk
Pretty sure this is fixed now.
Status: NEW → RESOLVED
Closed: 17 years ago
Resolution: --- → FIXED
Whiteboard: [cz-0.9.80]
You need to log in before you can comment on or make changes to this bug.