Uploaded image for project: 'Sourcetree For Mac'
  1. Sourcetree For Mac
  2. SRCTREE-4184

Diff view loses scroll position after refresh

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: High High
    • Next minor release
    • 2.3.2, 2.4
    • General

    • macOS Sierra - 10.12

      External Git - 2.10.0

      SourceTree - 2.3.2 (75)

    • Severity 2 - Major

      Beginning with version 2.3.2, the diff viewer now resets its scroll position when ever SourceTree refreshes. This occurs when files are updated (per the setting in preferences), when staging or unstaging a file, hunk, or some lines, and when manually refreshing from View > Refresh or cmd+R.

      This is especially problematic when staging changes one hunk at a time, as you lose your place in the diff viewer every time you stage anything. This makes the task of staging only some changes considerably more time consuming and error prone.

      The bug is a near-constant headache as it occurs every time you use the diff viewer (whether staging or not, whenever the program refreshes).

            [SRCTREE-4184] Diff view loses scroll position after refresh

            waldyrious added a comment -

            Thanks for the update, Raman Sidarakin! Too bad this took 6 years to be fixed, which means I had to live with this bug for the entire period when I used macOS. I have now been able to get back to Linux, and unfortunately SRCTREE-2991 has been closed, so I guess I won't be able to benefit from this fix anyway... 😞

            In any case, I've added a comment to the commit that bumped the Homebrew cask for SourceTree to 4.2.1 to mention this important bug fix: https://github.com/Homebrew/homebrew-cask/commit/57a0012d8ebacbba1e41d867df4c742af4a88868

            waldyrious added a comment - Thanks for the update, Raman Sidarakin! Too bad this took 6 years to be fixed, which means I had to live with this bug for the entire period when I used macOS. I have now been able to get back to Linux, and unfortunately SRCTREE-2991 has been closed, so I guess I won't be able to benefit from this fix anyway... 😞 In any case, I've added a comment to the commit that bumped the Homebrew cask for SourceTree to 4.2.1 to mention this important bug fix: https://github.com/Homebrew/homebrew-cask/commit/57a0012d8ebacbba1e41d867df4c742af4a88868

            Raman Sidarakin (Inactive) added a comment -

            Fixed in Sourcetree 4.2.1

            Raman Sidarakin (Inactive) added a comment - Fixed in Sourcetree 4.2.1

            debug45 added a comment -

            Not spammers. I just hate this damn bug. 😡

            debug45 added a comment - Not spammers. I just hate this damn bug. 😡

            dougp added a comment -

            Great, Jira spammers. GTH Marcus Mattsson and debug45.

            dougp added a comment - Great, Jira spammers. GTH Marcus Mattsson and debug45.

            debug45 added a comment - - edited

            And I switched to the https://fork.dev only because of this shameful bug too. As it turned out, the best app.

            debug45 added a comment - - edited And I switched to the https://fork.dev only because of this shameful bug too. As it turned out, the best app.

            Marcus Mattsson added a comment - - edited

            I happily left this app behind for https://git-fork.com/ because of issues like this

            Marcus Mattsson added a comment - - edited I happily left this app behind for  https://git-fork.com/  because of issues like this

            Tomáš Mika added a comment -

            This behaviour is so annoying, can't understand it does not have priority. This is reason why I dally with other graphical Git managers!

            Tomáš Mika added a comment - This behaviour is so annoying, can't understand it does not have priority. This is reason why I dally with other graphical Git managers!

            yjutard (Inactive) added a comment -

            voting for this one as well!

            yjutard (Inactive) added a comment - voting for this one as well!

            Merlin Mah added a comment -

            ++Apparently the fix missed the 4.0 (232) train as well...

            Merlin Mah added a comment - ++Apparently the fix missed the 4.0 (232) train as well...

            navyseai added a comment -

            cant wait to see this fix

            navyseai added a comment - cant wait to see this fix

              Unassigned Unassigned
              68b6250a8e79 Chris
              Affected customers:
              34 This affects my team
              Watchers:
              38 Start watching this issue

                Created:
                Updated:
                Resolved: