I think previously pressing ctrl+i / cmd+i, finding some text and pressing escape left document scrolled in that last found position. Current builds seem to scroll back to the position where inline search was triggered. That drives me nuts.

Yeah, it did change recently. I meant to make the change some time ago, but somehow only did it for Linux at the time. In essence, pressing escape cancels the search, and takes you back to the previous state. Pressing enter will close the panel and keep the selection where it now is.

I think previously pressing ctrl+i / cmd+i, finding some text and pressing escape left document scrolled in that last found position. Current builds seem to scroll back to the position where inline search was triggered. That drives me nuts.

Yeah, it did change recently. I meant to make the change some time ago, but somehow only did it for Linux at the time. In essence, pressing escape cancels the search, and takes you back to the previous state. Pressing enter will close the panel and keep the selection where it now is.

This makes me go insane because I use ctrl+i and ctrl+f interchangeably and they have different behavior. ctrl+f doesn't scroll back. And behavior when pressing 'enter' is also very different (in inline-search it ends search, in ctrl+f it goes to the next match) so that makes it even worse.

As much as you probably hate to introduce setting for every little thing, I would very match prefer old behavior to be selectable through pref.