<p dir="auto">When working in a CSS file (or presumably any type of file), if the file is updated from an outside source, the position of the page will reset causing you to have to scroll back down to where you were.</p>
<p dir="auto">Case: When working in CSS, I often work both directly in the CSS and via Chrome Dev Tools (changes are autosaved to the local CSS). Every time the file changes via Chrome Dev Tools, Atom resets the scroll position.</p>
<p dir="auto">Sublime Text handles this perfectly. Any changes are just updated but your position is never lost. This can probably be solved by just capturing the current line number before the file resets, then going back to that number.</p>
<p dir="auto">steps to reproduce</p>
<ol dir="auto">
<li>open a log file in atom</li>
<li>scroll part way down the file</li>
<li>add new line to end of log file with an external tool/editor and save</li>
<li>go back and view the log file in atom</li>
</ol>
<p dir="auto">expected</p>
<ul dir="auto">
<li>log file is reloaded</li>
<li>log file scroll position is still part way down (same as in step 2 above)</li>
</ul>
<p dir="auto">actual</p>
<ul dir="auto">
<li>log file is reloaded (PASS)</li>
<li>log file scroll position goes back to top (FAIL)</li>
</ul>
<p dir="auto">Every time a new line is added externally the editor reloads it (as it should) but it jumps to the top which makes it impossible to read log files while they're been written because atom constantly jump back to the top.</p>