Search Issue Tracker

Won't Fix

Won't Fix in 6000.0.X

Votes

0

Found in

6000.0.64f1

Issue ID

UUM-130351

Regression

Yes

Incorrect selection range is reported when selecting text across lines in a multiline TextField

Text (ATG)

-

Reproduction steps:
1. Open the attached “IN-127592” project
2. Open the “TextFieldTest” window (Test > Test Text Field)
3. Select digits 1 to 8 (included)
4. Press the “F12” key on the keyboard
5. Observe the Console window

Actual result: Message prints out the selected range and indicates 1 to 9
Expected result: Message prints out a range of 1 to 10 because the line break counts as a character

Reproducible with: 2023.1.0a9 (b67b5a2b1f70), 6000.0.64f1, 6000.3.0a4
Not reproducible with: 2023.1.0a8 (00f37d18b47f), 6000.3.0f1, 6000.4.0b1, 6000.5.0a3
Fixed in: 6000.3.0a5

Reproducible on: Windows 11
Not reproducible on: No other environments tested

  1. Resolution Note:

    Thank you for reporting a bug to Unity.

    We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.

    Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.

    Note that this is fixed in 6000.3+. The fix involves a big refactor that we cannot backport to 6000.0.

  2. Resolution Note (6000.0.X):

    Thank you for reporting a bug to Unity.

    We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.

    Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.

    Note that this is fixed in 6000.3+. The fix involves a big refactor that we cannot backport to 6000.0.

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.