Bug 106552 - [PropertiesView] Expanding a category that results in a scroll activates an arbitrary cell
Summary: [PropertiesView] Expanding a category that results in a scroll activates an a...
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.1   Edit
Hardware: PC Windows XP
: P3 normal with 3 votes (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-08-09 16:10 EDT by Eric Moffatt CLA
Modified: 2019-09-06 15:30 EDT (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Eric Moffatt CLA 2005-08-09 16:10:29 EDT 
I was going through the test plan (using the Manual Component tests) and 
noticed that if you arrange to have a collapsed category (or compound prop), 
opening of which will cause a scroll change (i.e. have it close to the bottom 
of the view), then expanding the tree will activate the editor  that ends up 
being under the cursor after the open in complete (a button 'up' activation??).
Comment 1 Eric Moffatt CLA 2005-08-09 16:12:49 EDT 
Also happens if you close an entry causing a scroll...
Comment 2 Adam Cabler CLA 2007-04-18 16:11:16 EDT 
This is a real problem for me.  Any chance of getting this in 3.3?

(In reply to comment #1)
> Also happens if you close an entry causing a scroll...
> 

(In reply to comment #0)
> I was going through the test plan (using the Manual Component tests) and 
> noticed that if you arrange to have a collapsed category (or compound prop), 
> opening of which will cause a scroll change (i.e. have it close to the bottom 
> of the view), then expanding the tree will activate the editor  that ends up 
> being under the cursor after the open in complete (a button 'up' activation??).
Comment 3 Eclipse Webmaster CLA 2019-09-06 15:30:29 EDT 
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.