| Summary: | compare widget jumps to top of page when I click "next change" | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [ECD] Orion | Reporter: | Susan McCourt <susan> | ||||
| Component: | Client | Assignee: | libing wang <libingw> | ||||
| Status: | RESOLVED FIXED | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | P3 | CC: | libingw, Szymon.Brandys | ||||
| Version: | 0.5 | Flags: | susan:
review+
|
||||
| Target Milestone: | 0.5 RC2 | ||||||
| Hardware: | PC | ||||||
| OS: | Windows 7 | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
|
Description
Susan McCourt
not only does this make me lose my context, but I can no longer see the twistie that expanded my change, so I have to scroll back up if I want to close it. I can't make this happen every time, need to work on some reproducible steps. At the moment I wrote the bug (running git status 2 in HEAD), I was in state that this happened every time. However it did not happen the next time I reloaded the page. I know the trick. In order to support up/down arrow keys navigation in selection model level, I'm checking if row is not fully visible I am using DIV.scrollToView. This checking function is triggered on every selection/cursor change. We need to fine tune this behavior in RC2. It just so happened in status page as the widget is a big view. Has nothing to do with compare widget, nor does it with the section. (In reply to comment #4) > It just so happened in status page as the widget is a big view. Has nothing to > do with compare widget, nor does it with the section. big view --> big row. Created attachment 217278 [details]
Patch
Susan, could you review the patch?
Susan, could you review the fix on origin/bug382540&382034 ? I am using one commit for both bug 382540 and bug 382034 because they are in the same selection model area. +1. This makes a big difference in keeping context while reviewing changes. Pushed to master. Thanks for the review, Susan. |