One of the most annoying things about VE is that the article text reflows when the editor starts. So every time I want to make an edit, I have to start by doing a search to find where I was before I clicked the "edit" link. Consider this sequence of screenshots:

In the first one, I have found a word I want to change ("operation") and highlighted it. In the second, I have scrolled back to find the nearest "edit" link. In the third, the editor has started. Note that at this point, the word I want to change is no longer visible on the screen. In fact (not shown in a screenshot) if I scroll back down to it, it's no longer highlighted, so I have to start searching for it. In this case, there are five instances of "operation" in the article that I have to look at before I find the right one. Imagine if I wanted to change "the", which appears 325 times?

Sometimes what I do is select a bunch of surrounding text, copy it, click "edit", then do a find and paste that text into the search bar. But that often doesn't work because the copied text includes the interpolated output of templates, which VE's find doesn't recognize.

I am not a javascript/DOM expert, but wouldn't it be trivial to make a call to window.getSelection() before invoking the editor, remembering that, re-select that text after the editor starts, and use element.scrollIntoView() to get back to it? This would be a huge win for productivity.