Bug 4393

Summary: REGRESSION: Unconfirmed text ignored in input type=text
Product: WebKit Reporter: Alexey Proskuryakov <ap>
Component: FormsAssignee: Darin Adler <darin>
Status: VERIFIED FIXED    
Severity: Major CC: farizdeni
Priority: P1    
Version: 420+   
Hardware: Mac   
OS: OS X 10.4   
URL: http://www.google.com
Attachments:
Description Flags
test case
none
fix that uses the same method we used a while back to fix <textarea> sullivan: review+

Alexey Proskuryakov
Reported 2005-08-11 11:02:51 PDT
If a form field contains unconfirmed inline input, its contents is ignored. Steps to reproduce: 1. Open the attached file (inputtext.html) in Safari 2. With any input method that uses inline input (such as Kotoeri Hiragana), type something tinto the input field 3. Click the "Start Search" button Results: An alert "Search field appears empty". Alternatively: try a Google search (from www.google.com, not the Google bar) without confirming the inline input Regression: was OK in WebKit/412 (OS X 10.4.2) Discussion: Necessity to manually confirm all inline input sessions is a major hurdle for people using inline input.
Attachments
test case (709 bytes, text/html)
2005-08-11 11:12 PDT, Alexey Proskuryakov 		no flags
Details
fix that uses the same method we used a while back to fix <textarea> (2.31 KB, patch)
2005-09-04 14:45 PDT, Darin Adler 		sullivan: review+
DetailsFormatted DiffDiff
View All Add attachment proposed patch, testcase, etc.
Alexey Proskuryakov
Comment 1 2005-08-11 11:12:23 PDT
Created attachment 3345 [details] test case
Alexey Proskuryakov
Comment 2 2005-09-04 08:10:27 PDT
Still present in Safari 2.0.1 (412.5) with ToT WebKit.
Darin Adler
Comment 3 2005-09-04 13:35:26 PDT
This sounds a lot like <rdar://problem/4094066> REGRESSION (1.2.5-1.3): unconfirmed inline input is ignored in <textarea>, lost when form is submitted, which I fixed a while back.
Darin Adler
Comment 4 2005-09-04 14:44:44 PDT
I've got a fix.
Darin Adler
Comment 5 2005-09-04 14:45:17 PDT
Created attachment 3764 [details] fix that uses the same method we used a while back to fix <textarea>
Note You need to log in before you can comment on or make changes to this bug.