RESOLVED CONFIGURATION CHANGED 33209
Cursor doesn't move and viewport doesn't scroll horizontally when very long word is entered in editable area 
https://bugs.webkit.org/show_bug.cgi?id=33209
Summary Cursor doesn't move and viewport doesn't scroll horizontally when very long w...
Alex Steitz
Reported 2010-01-05 07:47:42 PST
Steps to reproduce this bug: 1. Open a html editor / editable area e.g. http://demo.qooxdoo.org/current/showcase/#htmleditor 2. Remove all text (optional) 3. Enter a very long word WITHOUT any space in between until scrollbars are shown == Result after the scrollbar appears == The cursor is not moving with the entered text. Instead the cursor remains at the position where the original document (without scrollbars) would end. However, you can click and select at the text at the right of the cursor. Clicking at any position at the right of the cursor and entering text is functional. The text is entered at the right position only the cursor remains at the wrong position.
Attachments
Reduction (384 bytes, text/html)
2012-05-01 22:30 PDT, Ryosuke Niwa 		no flags
Details
View All Add attachment proposed patch, testcase, etc.
Ryosuke Niwa
Comment 1 2012-05-01 22:30:59 PDT
Created attachment 139747 [details] Reduction
Ryosuke Niwa
Comment 2 2012-05-01 22:43:39 PDT
*** Bug 38487 has been marked as a duplicate of this bug. ***
Ahmad Saleem
Comment 3 2022-08-30 05:28:06 PDT
I am not able to reproduce this issue anymore using attached reduction test case on STP 152 and it shows cursor moving on right side character by character and the scrollbar appear shortly once it is outside of editable area. It is same behavior in Chrome Canary 107. For some reason, Firefox Nightly 106 does not show any text inside editable area and just remain completely blank. Since I am not sure on Firefox behavior whether we need to now match Firefox here or not. I am going to leave this bug as it is as and tag others to comment. Thanks!
Alexey Proskuryakov
Comment 4 2022-08-30 16:12:03 PDT
This still reproduces with the reduction for me, but not when typing manually. I think that's a fine behavior, especially given that it matches Chrome.
Note You need to log in before you can comment on or make changes to this bug.