Auto-scrolls to top on refresh, if at bottom
So, this is a user-interface issue rather than how the actual rendering happens.
I'm writing a new document, I'm spending most of the time at the bottom of that document, writing text to the end of it.
If Marked is open on that document, and I'm scrolled to anywhere other than the bottom, on refresh it stays in position, which is correct.
But if the Marked preview window is scrolled right down to the bottom of the rendered document, and I refresh to show the stuff I've just written and saved, it instead snaps right back to the top of the document, and I have to scroll down to see the new bit.
This actually feels like a bug. It would at least be consistent if it remained anchored to the position in the document of the top of the window, though that would be wrong too as the new content would still be below the visible area.
Suggestion is: if the Marked window is scrolled all the way to the bottom, then upon refresh, it's still scrolled all the way to where the bottom is after the refresh. ie: the document would move up to show the new content.
If it's even a little way off the bottom, it can do what it does now.
Keyboard shortcuts
Generic
| ? | Show this help |
|---|---|
| ESC | Blurs the current field |
Comment Form
| r | Focus the comment reply box |
|---|---|
| ^ + ↩ | Submit the comment |
You can use Command ⌘ instead of Control ^ on Mac
Support Staff 1 Posted by Brett on 22 Jul, 2014 03:23 PM
This is the current behavior in Marked 2, on my machine:
Click here if that doesn't display properly.
The scrolling you see after I save the file is all automatic. It scrolls to the point and then detects that it's at the end of the document and raises the edit point up to 2/3 of the viewport size. If you type a whole page after the end, it doesn't scroll the the very end of what you've typed, but the beginning of what's new. This is partly because of other user requests, and partly because Marked only has a single "diff" point to work with. It doesn't know what else beyond the first diff might be new, so scrolling to the bottom may be detrimental to the feature.
Is this not what you're seeing? And which version of Marked are you using?
2 Posted by rachel on 22 Jul, 2014 03:55 PM
No, it's always scrolling back to the top, even with short amounts (eg: 5 words) of new text added at the end, let alone when there's lots.
This is Version 1.4.3 (228) bought fresh off the mac app store a couple of days ago (so there shouldn't be stale settings lying around).
Oh. I see that version has now gone from the app store and Marked 2 is there now. That's annoying, for a purchase of a couple of days ago...
I guess that makes the rest of what I'd written defunct. Although FWIW when I found and turned on "Scroll to first edit" the behaviour was pretty close to what you describe.