This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 97169 - Ant navigator window vertical scroll position gets reset
Summary: Ant navigator window vertical scroll position gets reset
Status: RESOLVED WONTFIX
Alias: None
Product: projects
Classification: Unclassified
Component: Ant (show other bugs)
Version: 6.x
Hardware: All All
: P4 blocker (vote)
Assignee: Jesse Glick
URL:
Keywords: UI, USABILITY
Depends on:
Blocks:
 
Reported: 2007-03-04 12:50 UTC by kirillkh
Modified: 2008-11-07 04:03 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description kirillkh 2007-03-04 12:50:37 UTC
1. open an Ant build file in the editor
2. open another Ant build file with many targets (e.g. build-impl.xml) in the
editor and bring up the Navigator window: the Navigator window should show a
vertical scrollbar
3. scroll the navigator down and single-click any target
4. switch back to the first file
5. switch to the second file again: the Navigator restores its scroll position
6. single-click a target in Navigator just below the first one: Navigator
vertical scroll position gets reset to 0%

I seem to recall also observing the issue in 5.5.
Comment 1 kirillkh 2007-03-04 13:05:05 UTC
Another scenario:
1. open an Ant build file with many targets (e.g. build-impl.xml) in the
editor and bring up the Navigator window: the Navigator window should show a
vertical scrollbar
2. scroll the navigator down and single-click any target
3. click anywhere in the editor and make a change (e.g. input a space character)
4. wait 5 seconds: the selected target in the Navigator loses selection
5. single-click a target in Navigator: the
vertical scroll position gets reset to 0%
Comment 2 Jesse Glick 2007-03-05 00:37:13 UTC
An old issue.
Comment 3 kirillkh 2007-03-16 16:12:35 UTC
I think this bug deserves a higher priority than P5 -- personally, I encounter
it daily, when running non-standard targets from a customized build.xml.
Comment 4 Jesse Glick 2007-06-13 01:45:17 UTC
Cf. issue #65795.
Comment 5 Marian Petras 2007-08-28 17:37:16 UTC
This bug is really annoying. I cannot believe it was marked as P5! (I would rate it as P3.)
Comment 6 Jesse Glick 2008-11-07 04:03:38 UTC
Can't reproduce first scenario. Will not fix second scenario; would be a lot of work for marginal benefit.