fix(editor): correct row offset calculation in translation editor

[meel-hd]

Proposed changes

The logic used to the calculate scroll offset based on the closest tbody tag which is fine unless the space between them is very large (like in issue #3507) which hides the translation input. As a fix we calculate based on a closer element that can't grow in height very much to hide the translation input.

Checklist

• Lint and unit tests pass locally with my changes.
• I have added tests that prove my fix is effective or that my feature works.
• I have added documentation to describe my feature.
• I have squashed my commits into logic units.
• I have described the changes in the commit messages.

Other information

[nijel]

The main intention here is to show the source string while the user navigates using the tab key. Your change destroys this (and mostly reverts to browser default behavior).

The whole thing is problematic because the content we want to show doesn't have to fit on the screen.

Ideas which could make it behave nicer:

• Move the viewport in a way that the editor is at the bottom, showing as much content above as possible.
• Do not adjust the viewport when the current editor was already focused.

[meel-hd]

Or the editor should stick in the bottom of the screen when it goes out of view. It will insure the user can scroll freely to view anything and be able to edit anywhere
Example

Recording.2024-11-11.141026.mp4

[nijel]

Great idea, it definitely makes sense as long as the editor is focused.