NewLines before and after does not allow keyboard editing of the element
Reported by
kapil.ta...@comprotechnologies.com,
Jun 28 2017
|
|||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/59.0.3071.115 Safari/537.36 Steps to reproduce the problem: A span element is created and it is made editable using the property contenteditable = "true". On launching ,in order to attain the cursor at the span element to edit, an   along with newlines before and after it are given to it in that span element. When the focus is given to it using the javascript .focus() function, the cursor appears but the user is not able to make any changes using the keyboard(typing). for example as shown in this fiddle Fiddle 1 -> https://jsfiddle.net/skmztbqx/ This scenario when replicated but this time there are no leading or trailing newline characters for in the span element, then on giving the focus using the javascript .focus() method, the cursor appears and the editing can be done as expected as shown in the Fiddle 2-> https://jsfiddle.net/4rajbg4q/. This is a Chrome 59 specific issue This had been working fine in the 58 version of chrome. What is the expected behavior? The editing should be allowed irrespective of the presence of newline characters before and after of  . What went wrong? The editing cannot be done in the span element with leading and trailing newline characters of Did this work before? Yes 58 Does this work in other browsers? Yes Chrome version: 59.0.3071.115 Channel: stable OS Version: 10.0 Flash Version:
,
Jun 30 2017
Able to reproduce the issue on Windows 7, Mac 10.12.5 & Ubuntu 14.04 using chrome stable#59.0.3071.115 & Canary#61.0.3145.0. Unable to type text in the textbox though the focus is seen in the text box ( https://jsfiddle.net/skmztbqx/). Manual bisect info: ------------------ Good-59.0.3036.0 -Revision-455621 Bad-59.0.3037.0 -Revision-455955 Per revision bisect info: ------------------------ You are probably looking for a change made after 455644 (known good), but no later than 455645 (first known bad). CHANGELOG URL: The script might not always return single CL as suspect as some perf builds might get missing due to failure. https://chromium.googlesource.com/chromium/src/+log/8f4b7a0506f076b26b76dd6aaf624860a6d3fda1..013ac5eaf30c02dfa356ba5399da43eb9f368040 Possible suspect: ---------------- https://chromium.googlesource.com/chromium/src/+/013ac5eaf30c02dfa356ba5399da43eb9f368040 joone.hur@Could you please take a look and reassign to the right owner if it is not related to your change. Thanks..!!
,
Jul 5 2017
I am also facing similar issue in my application. Please prioritize this issue.
,
Jul 5 2017
I will take a look at this bug.
,
Jul 20 2017
Any update?
,
Dec 6 2017
Lower to Pri-3 since we don't have time to work this. |
|||
►
Sign in to add a comment |
|||
Comment 1 by nyerramilli@chromium.org
, Jun 29 2017