Bug 46801 - [Qt][S60] Wrong characters are inputted when long pressing the keys on QWERTY
Summary: [Qt][S60] Wrong characters are inputted when long pressing the keys on QWERTY
Status: RESOLVED DUPLICATE of bug 49787
Alias: None
Product: WebKit
Classification: Unclassified
Component: WebKit Qt (show other bugs)
Version: 528+ (Nightly build)
Hardware: S60 Hardware S60 3rd edition
: P1 Critical
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-09-29 05:37 PDT by Ankur Baranwal
Modified: 2010-12-07 08:26 PST (History)
4 users (show)

See Also:

Attachments
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 Ankur Baranwal 2010-09-29 05:37:59 PDT 
Qt: 4.7
QtWebkit: 2.1 (9.2.9)
OS: Symbian^3

Hardware keypad on the device must be used to reproduce this bug.

Steps to reproduce the error -
1. Open www.google.com in Anomaly Browser.
2. Select the search text box.
3. Long press any key that can be used for entering more than one characters.
     Example - short press the key - letter 't'.
               long press the key - number '2'.

Expected Result -
Single character should be displayed (say '2').

Actual Result -
Two characters are displayed for each long press (like 't2').

Additional Info -
Hardware keypad should be used on the device to reproduce the bug.
Comment 1 Ankur Baranwal 2010-09-29 07:26:55 PDT 
Tested using a sample Qt application. The bug is not reproducible. So this has something to do with QtWebkit.
Comment 2 Suresh Voruganti 2010-11-04 13:08:49 PDT 
Top issue for Services, fix is required for Qtwebkit 2.1.
Comment 3 Suresh Voruganti 2010-11-04 13:14:33 PDT 
Boston bugzilla error id is http://bugs.nokia-boston.com/bugzilla/show_bug.cgi?id=6025
Comment 4 priya.baskaran 2010-12-07 08:12:40 PST 
Not reproducible on the build that was created to fix the webkit bug
https://bugs.webkit.org/show_bug.cgi?id=49787. Verified.
Comment 5 Suresh Voruganti 2010-12-07 08:26:39 PST 
Fix for 49787 has fixed this issue, so duplicating this issue to 49787

*** This bug has been marked as a duplicate of bug 49787 ***