Warning: This build has drifted.
The coverage report for this pull request build may be inaccurate because its base commit is no longer the HEAD of its target branch.
This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

    • Learn more: For more information on this, see Tracking coverage changes for pull request builds.
    • Fix now: For a quick fix, rebase this PR at GitHub. Your next report should be accurate.
    • Prevent going forward: To avoid this issue with future PRs, see these Recommended CI Configurations.

Keep a wrapped line's trailing space on its row, and follow the cursor

Word wrap drops the space it wraps on, since it belongs to neither of the
two rows it separates. When that space is the last rune of the line there
is no second row to drop it in front of, so no row covered the position
after it and the cursor at the end of the line resolved outside of every
row. Keep it on the row that was just closed instead, which leaves the
number of rows unchanged.

Resizing a wrapped Entry moves the wrap points, so entryRenderer.Layout
resolves the cursor's position again afterwards. It decided whether to by
comparing textPosFromRowCol before and after, but that is docBegin plus the
column and docBegin of the first row is always zero, so the comparison
could never see a cursor on the first row move. Compare the resolved row
and column instead.