Closed yourhead closed 5 years ago
Currently I've identified two points that call a full serenader in a drag-end and a paste. There is no obvious reason to a full re-render here. A top-node refresh seems like it should be sufficient.
The code is not specific why this aggressive refresh is needed here.
i've added a fix in beta 3 for scroll jumping at one particular point: after paste/drag.
i suspect other scroll-jumping conditions may be caused by latent remote content loads. in S4 i'll add a switch to disable linked css, fonts, and images from edit mode.
A complete edit-mode re-render causes a momentary "jump" from the top of the page back to the point of the edit. However this sort of re-render should be rare and only happen in very specific situations when the content of the entire page is in doubt.
The bug is that this is happening too often.