it does that when article bottom goes out of screen. this is supposed to work with keyboard shortcuts, it shouldn’t happen when selecting things with mouse. i’ll try to take a look at this tomorrow.
e: i’m afraid i have bad news. this is why this happens: imagine selecting an article below an already expanded one:
== article 1 headline
== article 2
== article 3 headline <-- you click on this one
currently selected article collapses and your newly selected article moves somewhere because its logical offset in headline buffer changes.
if previously selected article was enough pixels above, your currently clicked one can easily go entirely off-screen. to keep this from happening newly selected article may be moved on top of headlines buffer, it’s kinda annoying but the alternative can be even more disorienting.
stuff like this was one of the reasons i wanted to remove combined (unexpanded) mode but as i know all too well you people can’t let go forcing me to suffer my bad decisions forever.
e: if you want to see how this works in practice comment out the body of
Article.cdmScrollToId method and click on different articles.
e2: i guess we could try preserving logical offset before expanded article is switched over but a) that would be annoying to implement, i think, and more importantly b) offset wouldn’t be possible to restore in some cases when active article moves up - there simply wouldn’t be enough pixels to scroll.
e3: i guess another alternative is not automatically collapsing no longer active articles. comments welcome.