Bug 238903 - Cursor navigation behaviour is unexpected during Delete composed character with Backspace key
Cursor navigation behaviour is unexpected during Delete composed character wi...
Status: CLOSED DUPLICATE of bug 222781
Product: Fedora
Classification: Fedora
Component: qt (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Ngo Than
Ben Levenson
: i18n
Depends On: 213197
  Show dependency treegraph
Reported: 2007-05-03 14:58 EDT by A S Alam
Modified: 2013-07-02 20:44 EDT (History)
5 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2007-05-03 19:32:30 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Test Case - Text File (150 bytes, text/plain)
2007-05-03 15:00 EDT, A S Alam
no flags Details

  None (edit)
Comment 1 A S Alam 2007-05-03 15:00:47 EDT
Created attachment 154064 [details]
Test Case - Text File
Comment 2 A S Alam 2007-05-03 15:02:32 EDT
Description of problem:
When delete composed character with Backspace key, then cursor navigation is not 
good, cursor is moved to some other character to RIght hand side

Version-Release number of selected component (if applicable):

How reproducible:
Everytime in composed character in word

Steps to Reproduce:
1.open kedit
2. paste test from test case
3. move cursor 1 position to right side from [HOME]
 4.Press Backspace once

Actual results:
cursor move to 3 position

Expected results:
it should be at same position

1) Please select keyboard 'Jhelum' from scim-Punjabi. Type following word:
kdho (ਪ੍ਰਧਾਨਗੀ)

(move to end, move cursor 1 left side and press backspace. Now check cursor. 

2) Problem exist in words where halant (0A4D) is used in Punjabi.
Comment 3 A S Alam 2007-05-03 15:06:21 EDT
Tested version:
Comment 4 A S Alam 2007-05-03 19:32:30 EDT

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

Note You need to log in before you can comment on or make changes to this bug.