the 1.14.1 version refactor the scrollIntoView function by adding:
rect = {left: rect.left - moveX, top: rect.top - moveY, right: rect.right - moveX, bottom: rect.bottom - moveY}
But it causes another probelm.
For example, I am using a Modal to insert something into pm.
But the Modal is werid which like its parent node doesn’t contain its Children while the code is like <Parent><Children /></Parent>.
In browser view it looks like:
So the position is always wrong when cumulating the pos;
I recommend judging if the parent contains its children in coords before calculate.
That might indeed go wrong for absolute or fixed positioned elements. Can you provide a minimal example of the kind of DOM structure and styling that reproduces the issue, so that I can debug it?
)
