My favorites | Sign in
Logo
             
New issue | Search
for
| Advanced search | Search tips
Issue 7755: Pasting and then clicking into Twitter.com textbox doesn't work correctly
2 people starred this issue and may be notified of changes. Back to list
Status:  Upstream
Owner:  ojan@chromium.org
Closed:  Mar 2009
Cc:  jon@chromium.org, karen@chromium.org
Type-Bug
Pri-2
OS-All
Area-WebKit
Mstone-X


Sign in to add a comment
 
Reported by mattcutts, Feb 15, 2009
Chrome Version       : 2.0.162.0
URLs (if applicable) : www.twitter.com
Other browsers tested:
Add OK or FAIL after other browsers where you have tested this issue:
Safari 3:
    Firefox 3: OK
IE 7:

What steps will reproduce the problem?

1. Open http://www.cnn.com/ in one tab in Chrome. Copy the url.
2. Get an account on Twitter.com, then open Twitter in another tab. In the 
"What are you doing?" box, type "One two three: ". Then paste the url 
"http://www.cnn.com/" into the box. Now type (do not paste) the text " four 
five six seven eight nine ten eleven twelve fourteen." into the text box.
3. Now click on the text between "twelve" and "fourteen" (as if you were 
going to add a new word between them).

What is the expected result?

I would expect the cursor to appear between the text "twelve" and 
"fourteen".

What happens instead?

Instead, the cursor position will move to just before the 
“http://www.cnn.com/” text. If you double-click between the twelve and 
fourteen, the “http” will be selected. Screenshot attached.

Additional information:

One weird thing is that this bug only fires when you have two lines filled 
in that Twitter text box. If the text was “One two three: 
http://www.cnn.com/ four five six seven eight nine ten eleven.” (which fits 
on one line) then you don’t see this issue. I also didn’t see this issue in 
Firefox.
twitter-chrome-bug.png
17.9 KB Download
Comment 1 by jon@chromium.org, Feb 18, 2009
More textbox fun for Ojan!
Status: Assigned
Owner: o...@chromium.org
Labels: -Area-Misc Area-WebKit Mstone-2.0
Comment 2 by ojan@chromium.org, Mar 03, 2009
The fix for this is rather involved and I'm relatively confident that this is not a
regression from 1.0. I'll keep working on this upstream, but I don't think we'd want
to pull in as involved a change as this to the 2.0 release.

Here's the relevant webkit bug: https://bugs.webkit.org/show_bug.cgi?id=24180
Labels: -Mstone-2.0 Mstone-2.1
Comment 3 by ojan@chromium.org, Mar 03, 2009
(No comment was entered for this change.)
Cc: j...@chromium.org
Comment 4 by jon@chromium.org, Mar 03, 2009
Upstreamed to WebKit.
Status: Upstream
Comment 5 by ojan@chromium.org, Jun 10, 2009
(No comment was entered for this change.)
Labels: -Mstone-2.1 Mstone-4
Comment 6 by ojan@chromium.org, Oct 07, 2009
(No comment was entered for this change.)
Labels: -Mstone-4 Mstone-X
Sign in to add a comment