Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 369605 - repo page loses my position when it refreshes
Summary: repo page loses my position when it refreshes
Status: RESOLVED INVALID
Alias: None
Product: Orion
Classification: ECD
Component: Client (show other bugs)
Version: 0.4   Edit
Hardware: PC Windows 7
: P3 normal (vote)
Target Milestone: 6.0 M2   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
: 371418 (view as bug list)
Depends on: 371498
Blocks: 368848 369591
  Show dependency tree
 
Reported: 2012-01-24 17:06 EST by Susan McCourt CLA
Modified: 2015-04-01 10:26 EDT (History)
0 users

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 Susan McCourt CLA 2012-01-24 17:06:09 EST 
I'm using the repo page a lot today while processing Orion contributions from different github clones of the client repo.  I find it a bit disorienting when I do something in one section (like fetch a remote) and the page refreshes, losing my position.  It would be good to keep me at the section I was on.
Comment 1 Szymon Brandys CLA 2012-02-14 04:00:19 EST 
*** Bug 371418 has been marked as a duplicate of this bug. ***
Comment 2 Susan McCourt CLA 2012-04-03 12:04:16 EDT 
I was going to open another bug on this topic, but I think perhaps it belongs here.  

Whenever I create a new branch in a repository, the entire repository page refreshes.  I have to wait for the commit list to load, etc.  Note that just creating the branch does not make it active.  There is no reason that anything other than the branch list should refresh.

In bug 371261 we talk about populating repo content from the top down to reduce flashing and notification.  In bug 371498, we talk about expanding/collapsing sections to reduce flashing.

But I think that there are probably some cases where we shouldn't even be refreshing more than one section.  If we fix those cases, it would help a lot.  

So I'm suggesting that the page be more picky about which sections it updates for any particular action.  Otherwise the "top down" strategy will never be satisfying for the user.
Comment 3 Szymon Brandys CLA 2015-04-01 10:26:34 EDT 
The new Git page does not have the problem.