New issue
Advanced search Search tips

Issue 896901 link

Starred by 1 user

Issue metadata

Status: Assigned
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 3
Type: Bug



Sign in to add a comment

If selection ends at soft line wrap, selection end handle is incorrectly placed in the next line

Project Member Reported by xiaoche...@chromium.org, Oct 18

Issue description

Chrome Version: 72.0.3584.0 Canary
OS: Android

What steps will reproduce the problem?
(1) Open "data:text/html, <textarea>"
(2) Type "foooooooooooo-baaaaaaaaaar" in it to ensure that text is wrapped after "-"
(3) Select "foooooooooooo-"

What is the expected result?

Selection handles are placed at the selection start and end

What happens instead?

Selection end handle is placed at the start of the second line

See attached screenshot
 
Screenshot_20181017-190008.png
142 KB View Download
Cc: changwan@chromium.org
Hi Changwan,

During code review (crrev.com/c/1289999), we have some discussion about UX. Quoting yoichio:

> This change prohibits user to create following selection handles, right?:
> ^foo-
> |bar
>
> I'm not sure this is a bug from the point of end user UX.
> Could you investigate Android text editor behavior, safari/iOS's, touch on windows 10?
> May be good to contact UX reviewers.

Do you think this should be considered as a bug?
Cc: amaralp@chromium.org ctzsm@chromium.org
I've tried it on Notes and got a similar result. Android text editor seems to behave similarly.
Screenshot_20181019-110423.png
100 KB View Download
In WebView/TextView's case, the text may very close to the edge of the screen, if the handle show on the same line, it is very hard for user to move the handle.

But that kind of use case may not be seen in real app. IMO, I would expect apps add  margin to avoid this.
Labels: -Pri-2 Pri-3
It seems that there's no definitively correct behavior to follow.

Maybe we just postpone it since it's not an important issue...

Sign in to add a comment