| Summary: | repo page loses my position when it refreshes | ||
|---|---|---|---|
| Product: | [ECD] Orion | Reporter: | Susan McCourt <susan> |
| Component: | Client | Assignee: | Project Inbox <orion.client-inbox> |
| Status: | RESOLVED INVALID | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | ||
| Version: | 0.4 | ||
| Target Milestone: | 6.0 M2 | ||
| Hardware: | PC | ||
| OS: | Windows 7 | ||
| Whiteboard: | |||
| Bug Depends on: | 371498 | ||
| Bug Blocks: | 368848, 369591 | ||
|
Description
Susan McCourt
*** Bug 371418 has been marked as a duplicate of this bug. *** 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. The new Git page does not have the problem. |