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.

docs(textarea): correct SetCursorByteOffset's account of row separators

The godoc said an offset landing on the "\n" Value inserts between rows
was a position the cursor cannot occupy, and that it snaps forward like
a mid-rune offset does.

It does not, because there is nothing to snap past. Offsets are
insertion points: the offset of the separator byte is the end of the row
before it, and the offset after it is the start of the row that follows.
Both are ordinary cursor positions, and the test covering them already
asserts exactly that — it was just named for the snap it never makes.

Only the mid-rune case snaps. Say so, and rename the test to match.