New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 785393 link

Starred by 2 users

Issue metadata

Status: Assigned
Owner:
Last visit > 30 days ago
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Feature
Team-Accessibility



Sign in to add a comment

Anchor affinity is lost when doing text editing

Project Member Reported by dmazz...@chromium.org, Nov 15 2017

Issue description

This is not a major issue but it'd be nice to behave more consistently for users with disabilities who rely on the keyboard.

Steps to repro:

1. Load this document:

data:text/html,<textarea cols=6 rows=10>a-b-c-d-e-f-g-h-i-j-k-l-m-n-o-p-q-r-s-t-u-v-w-x-y-z</textarea>

2. Start with the cursor at the beginning of the first line

3. Press the End key to move the cursor to the end of the first line, now affinity is upstream.

4. Now press shift+right or down to extend the selection

5. Then press left arrow to collapse the selection back to a cursor

Expected result:
The cursor goes back to the end of the first line (affinity upstream)

Actual result:
The cursor is at the start of the second line (affinity downstream)

Note that if there is an explicit line break between the first and second lines, this behavior doesn't occur.

It seems to me like a selection should just keep track of the anchor affinity, that would solve the issue.

 
Cc: kojii@chromium.org

Comment 2 by yosin@chromium.org, Dec 6 2017

Labels: -Type-Bug Type-Feature
Owner: ----
Status: Available (was: Untriaged)
Upload to https://jsfiddle.net/68tbaf13/

Edge: Work as #c1. First line contains "a-b-c " instead of "a-b-c-d-"
 adopt visible soft newline(?)
Firefox: Shift+Right move caret before first of second line == before "e".
 use soft newline character


Project Member

Comment 3 by sheriffbot@chromium.org, Dec 6

Labels: Hotlist-Recharge-Cold
Status: Untriaged (was: Available)
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Owner: nek...@chromium.org
Status: Assigned (was: Untriaged)
@Nektarios, any thoughts on this one?

Sign in to add a comment