After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 481222 - [Indic] Backspace key doesn't work correctly - cursors blink in the middle of glyph
[Indic] Backspace key doesn't work correctly - cursors blink in the middle of...
Status: RESOLVED OBSOLETE
Product: pango
Classification: Platform
Component: indic
unspecified
Other All
: Normal normal
: ---
Assigned To: Pango Indic
pango-maint
Depends on:
Blocks:
 
 
Reported: 2007-09-28 09:07 UTC by LingNing Zhang
Modified: 2018-05-22 12:33 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description LingNing Zhang 2007-09-28 09:07:41 UTC
Please describe the problem:
https://bugzilla.redhat.com/show_bug.cgi?id=288821

Opened by A S Alam (aalam@redhat.com)  	 on 2007-09-13 02:26 EST  	[reply]  	   Private

Description of problem:

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


How reproducible:


Steps to Reproduce:
1. start evolution in bn_IN locale and select New Mail
2. in the "Subject"/"Message Body" widget
3. Select Probhat IM 
4. Type : dir[k/tri 
5. Press left arrow (<-) key one time. 
6. Press backspace 

  
Actual results:
In "Subject" widget, two cursors are blinking, pls see attached screenshot1
In "Message Body" widget, cursor is blinking in the middle of glyph, pls see
attached screenshot2

Expected results:
Cursor should be at one end

Additional info:
it is CLONED bug


Comment #1 From A S Alam (aalam@redhat.com) 	on 2007-09-13 02:27 EST 	[reply] 	Private

it CLONE of following bug:
Bug 226932: [Indic] Backspace key doesn't work correctly - cursors blink in the
middle of glyph


Comment #2 From A S Alam (aalam@redhat.com) 	on 2007-09-13 02:42 EST 	[reply] 	Private

Package version:
pango-1.18.1-1.fc8
gedit-2.19.91-1.fc8


Comment #3 From Akira TAGOH (tagoh@redhat.com) 	on 2007-09-13 10:52 EST 	[reply] 	Private

Well, better filing separately for what you complain on screenshot1 and 2.

However we have inconsistent bug in Pango (this, particularly for screenshot1)
and Qt (Bug#222781). I thought we had discussed that before though, let me
explain that again.

Since the backspace key works for deleting a character but not the combined one,
it's pretty likely to recombine between the characters around the deleted one.
once it happens, current position isn't valid position to be stopped the cursor
anymore. but it's hard to determine which one is preferable to be moved, and
people usually may wants to correct something after deleting the backspace key.
the recombination should be a side-effect in the most cases IMHO.
So the cursor doesn't have to be moved anywhere and just keeps current position,
but needs to notify current state to the users.

IMHO there are two possible solutions for this:
1. improve UI that let people know the current cursor possition is somewhere in
the combined character, instead of blinking two cursor between a combined character.
2. give up to manage the backspace key as deleting a character, and have the
same behavior to the delete key. i.e. delete the combined character.

Which one do you prefer? or another opinion are welcome.


BTW for screenshot 2, there seems to be a character that is_cursor_position is
true unexpectedly.



Steps to reproduce:


Actual results:


Expected results:


Does this happen every time?


Other information:
Comment 1 Ankit Patel 2008-01-18 10:21:07 UTC
To me, double-cursor looks feature, rather than a bug...

However, if it's really unacceptable from the developer/end user point view, then I would prefer to go for the option 2 suggested by Tagoh, that is "give up to manage the backspace key as deleting a character, and have the same behavior to the delete key. i.e. delete the combined character."...
Comment 2 Behdad Esfahbod 2010-03-04 01:36:58 UTC
Dupe of bug 345066?
Comment 3 GNOME Infrastructure Team 2018-05-22 12:33:47 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/pango/issues/98.