RESOLVED FIXED 25061
Unconfirmed input-method typing should affect the value of <textarea>
https://bugs.webkit.org/show_bug.cgi?id=25061
Summary Unconfirmed input-method typing should affect the value of <textarea>
Michael Davidson
Reported 2009-04-06 15:08:31 PDT
Set your input language to Katakana. Type 'ka<return>' in the input and in the textarea. In the input, the "value" field updates as you type. In the textarea, the value doesn't update until you hit 'return'. The former is consistent with other browser and is the desired behavior. This happens on OSX and Windows.
Attachments
Make unconfirmed IME text affect textarea's value. (6.83 KB, patch)
2009-05-18 00:31 PDT, Ojan Vafai
mjs: review-
Ojan's fix with an automated test. (8.14 KB, patch)
2009-06-25 23:17 PDT, Hironori Bono
mjs: review+
Darin Adler
Comment 1 2009-04-06 15:17:30 PDT
I think this bug would be clearer if it the title talked about <input> and not <textarea>, since <textarea> is behaving as desired. The bug here isn't that it's inconsistent, but rather that it's wrong for <input>! I'm going to take a cut at retitling the bug.
Darin Adler
Comment 2 2009-04-06 15:18:30 PDT
Is this a change from previous versions of WebKit, or has it always been this way? Is this the same on Windows, or is this Mac-specific?
Michael Davidson
Comment 3 2009-04-06 15:46:45 PDT
It's actually the other way around - input has the desired behavior, textarea does not. It happens on Mac and Windows.
Michael Davidson
Comment 4 2009-04-06 15:47:30 PDT
That is, all other browsers give the intermediate value (which is what input does in WebKit). This is helpful for autocomplete.
Alexey Proskuryakov
Comment 5 2009-04-06 23:53:31 PDT
Retitling the bug again. I see how this can be desired behavior, but do all other browsers work like this? In Firefox 3.1b3 on Mac OS X, nether textareas nor inputs have their value affected by unconfirmed text.
Michael Davidson
Comment 6 2009-04-07 08:29:37 PDT
Firefox 3.08 on the Mac definitely works like this. IE works like this, as does current FF on Windows. This is definitely the desired behavior. If FF 3.1 doesn't work like this, I'll file a bug over there too.
Julie Parent
Comment 7 2009-04-07 10:48:22 PDT
FYI - for contentEditable, on Chrome, I'm seeing the input behavior (fetching innerHTML rather than value).
Ojan Vafai
Comment 8 2009-05-18 00:31:56 PDT
Created attachment 30441 [details] Make unconfirmed IME text affect textarea's value.
Alexey Proskuryakov
Comment 9 2009-05-18 02:09:18 PDT
Comment on attachment 30441 [details] Make unconfirmed IME text affect textarea's value. Please make an automated test for this (at least Mac-only, if it cannot be made cross-platform).
Maciej Stachowiak
Comment 10 2009-05-21 19:56:53 PDT
Comment on attachment 30441 [details] Make unconfirmed IME text affect textarea's value. Marking r- per Alexey's comment about tests. Someone should review the substance of the code change as well.
Hironori Bono
Comment 11 2009-06-25 23:17:24 PDT
Created attachment 31911 [details] Ojan's fix with an automated test. This change just replaces Ojan's manual tests with an automated test. Since I'm wondering if textInputController.setMarkedText() works on all platforms, this automated test is put under "LayoutTest/platform/mac/editing/input".
Maciej Stachowiak
Comment 12 2009-07-05 04:30:36 PDT
Comment on attachment 31911 [details] Ojan's fix with an automated test. Looks good. r=me
Eric Seidel (no email)
Comment 13 2009-07-06 14:35:19 PDT
Landed as r45567.
Note You need to log in before you can comment on or make changes to this bug.