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 338014 - GTerminal text events inconsistent, non-standard (from other gnome apps)
GTerminal text events inconsistent, non-standard (from other gnome apps)
Status: RESOLVED DUPLICATE of bug 372777
Product: vte
Classification: Core
Component: general
unspecified
Other All
: Normal normal
: ---
Assigned To: VTE Maintainers
VTE Maintainers
: 338230 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2006-04-10 19:49 UTC by Brett Clippingdale
Modified: 2007-01-26 10:20 UTC
See Also:
GNOME target: ---
GNOME version: 2.13/2.14



Description Brett Clippingdale 2006-04-10 19:49:26 UTC
Please describe the problem:
Text events are inconsistent if delete/backspace has been pressed; inconsistent
(essentially inverted) with other gnome applications (eg. gedit).  Both event
types and ordering are divergent.  

Also, once <backspace> or <delete> is pressed, gnome-terminal fires different
events after each typed character, and maintains this "mode" on all subsequent
typing until <CR> resets it.

The following show the order of fired events:

typing:
gterm: moved,inserted events *OR* moved,deleted,inserted
gedit: inserted, moved

backspace/delete, typing after backspace/delete: 
gterm: moved, deleted, inserted
gedit: deleted, moved

Steps to reproduce:
Steps to reproduce:
1. run at-poke, don't poke anything, just check "Log events"
2. "Accessible Events" window opens, look in "Events to listen for:", expand
"object" and check "text-caret-moved" and "text-changed" events
3. type in GTerminal, watch at-poke's event log
4. type in any other gnome-based editor (eg. gedit), compare the order in each
set of fired events
5. compare event types fired when pressing backspace/delete, typing after
backspace/delete 


Actual results:
Ordered Events:
typing: moved, inserted  
backspace/delete: moved, deleted, inserted
typing after backspace/delete: moved, deleted, inserted

Expected results:
Ordered Events:
typing: inserted, moved
backspace/delete: deleted, moved
typing after backspace/delete: inserted, moved (don't change after bksp/del)

Does this happen every time?
yes

Other information:
Comment 1 Brett Clippingdale 2006-04-12 15:09:01 UTC
This is important for accessibility, since alternate UIs (such as a screen reader) must communicate the cursor changes to the user.  If the events are inconsistent, an a11y user might not be given accurate caret information, which will also complicate navigation within a text element.
Comment 2 Brett Clippingdale 2006-04-12 15:12:15 UTC
This bug is cross-posted with at-spi (atkbridge), #338230:
http://bugzilla.gnome.org/show_bug.cgi?id=338230
Comment 3 bill.haneman 2006-06-12 14:56:29 UTC
*** Bug 338230 has been marked as a duplicate of this bug. ***
Comment 4 Mariano Suárez-Alvarez 2007-01-26 07:17:34 UTC
Moving to vte, which is in charge of this.
Comment 5 Chris Wilson 2007-01-26 10:20:57 UTC
Anachronistic dup, bug 372777 has a good description of the correct ordering.

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