New issue
Advanced search Search tips

Issue 703175 link

Starred by 2 users

Issue metadata

Status: Available
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: All
Pri: 3
Type: Bug


Participants' hotlists:
Hotlist-1


Sign in to add a comment

Nested contenteditable gets focus on reverse selection

Reported by tha...@athenahealth.com, Mar 20 2017

Issue description

UserAgent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.87 Safari/537.36

Steps to reproduce the problem:
1. Go to https://jsbin.com/pofapufani/edit?html,js,console,output
2. Click and drag from "start" into "middle"
3. Observe that no event is logged in the Console window
4. Click and drag from "end" into "middle"
5. Observe that a focus event is logged in the Console window

What is the expected behavior?
Selection should extend into "middle" but not fire any focus event.

What went wrong?
A focus event is fired on the "middle" span.

Did this work before? N/A 

Chrome version: 56.0.2924.87  Channel: stable
OS Version: 6.1 (Windows 7, Windows Server 2008 R2)
Flash Version: 

This doesn't seem to be true on all contenteditables, I've only replicated it in this case, with contenteditable > non-contenteditable > contenteditable
 
Components: -Blink Blink>Editing>Selection
Labels: -OS-Windows OS-All
Seems to occur on Linux as well.
Labels: Needs-Triage-M57
Labels: M-59
Status: Untriaged (was: Unconfirmed)
Able to reproduce this issue on Windows-10, Mac OS 10.12 and Ubuntu 14.04 using chrome stable #57.0.2987.110 by following steps mentioned in the original comment. Observed the focus event is not fired.

This issue is seen on older version of chrome including M35-35.0.1849.0. Hence marking it as untriaged.

Comment 4 by yosin@chromium.org, Mar 22 2017

Status: Available (was: Untriaged)

Comment 5 by yosin@chromium.org, Oct 4 2017

Labels: Pri-3
Project Member

Comment 6 by sheriffbot@chromium.org, Oct 4

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
Status: Available (was: Untriaged)

Sign in to add a comment