Bug 60405 - Pasting from clipboard to a non-empty textfield doesn't work under certain circumstances
Summary: Pasting from clipboard to a non-empty textfield doesn't work under certain ci...
Status: RESOLVED WORKSFORME
Alias: None
Product: WebKit
Classification: Unclassified
Component: Forms (show other bugs)
Version: 525.x (Safari 3.2)
Hardware: Mac (Intel) OS X 10.6
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-05-06 14:36 PDT by Christian Müller
Modified: 2011-05-08 02:23 PDT (History)
1 user (show)

See Also:

Attachments
Minimal valid XHTML, which allows to reproduce the bug. (419 bytes, text/html)
2011-05-06 14:37 PDT, Christian Müller 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Christian Müller 2011-05-06 14:36:26 PDT 
The following bug can be reproduced on any new Safari and an old version of Chrome (7.0.517.41) @Ubuntu.

Here is the minimal valid XHTML file for bug reproducing: or see the attachment.

Steps:

1. Open the file and make sure you see the text field.
2. Type something into the text field.
3. Copy any string into the clipboard.
4. Try to paste the clipboard content to the text field.

However, the pasting works if the textfield is empty.

The problems seems to be caused by the following (fully irrelevant for the textfield) CSS snippet:

#id > :last-child { }
Comment 1 Christian Müller 2011-05-06 14:37:44 PDT 
Created attachment 92642 [details]
Minimal valid XHTML, which allows to reproduce the bug.
Comment 2 Alexey Proskuryakov 2011-05-06 17:30:37 PDT 
I can reproduce this in Safari/WebKit 5.0.5, but not when using a WebKit nightly. Could you please verify that it's the same for you?
Comment 3 Christian Müller 2011-05-07 23:31:05 PDT 
Indeed, the bug is not reproducible with WebKit nightly! May I ask you what does it imply? Will it be fixed in the nearest Safari update? Thanks!
Comment 4 Alexey Proskuryakov 2011-05-08 02:23:21 PDT 
Thanks for verifying that this no longer occurs!

I can not make comment on future Safari releases, sorry.