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 726844 - Do not emit object:text-changed signals for newly-shown or newly-selected table cells
Do not emit object:text-changed signals for newly-shown or newly-selected tab...
Status: RESOLVED DUPLICATE of bug 746706
Product: gtk+
Classification: Platform
Component: Accessibility
3.11.x
Other Linux
: Normal normal
: ---
Assigned To: gtk-bugs
gtk-bugs
Depends on:
Blocks:
 
 
Reported: 2014-03-21 19:31 UTC by Joanmarie Diggs (IRC: joanie)
Modified: 2018-02-10 15:57 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
accessible-event listener (355 bytes, text/x-python)
2014-03-21 19:31 UTC, Joanmarie Diggs (IRC: joanie) 		Details

Description Joanmarie Diggs (IRC: joanie) 2014-03-21 19:31:29 UTC 
Created attachment 272593 [details]
accessible-event listener

Steps to reproduce:

1. Launch the attached accessible-event listener in a terminal
2. Launch gtk3-demo
3. Arrow amongst the items in the tree on the left
4. Expand collapsed items in that same tree

Expected results: There would not be any object:text-changed signals

Actual results: There is an object:text-changed signal for each newly-shown and newly-selected table cell.
Comment 1 Matthias Clasen 2018-02-10 05:13:10 UTC 
We're moving to gitlab! As part of this move, we are moving bugs to NEEDINFO if they haven't seen activity in more than a year. If this issue is still important to you and still relevant with GTK+ 3.22 or master, please reopen it and we will migrate it to gitlab.
Comment 2 Joanmarie Diggs (IRC: joanie) 2018-02-10 15:57:46 UTC 
Seems to be a dup of 746706. I still need to figure out what the current state of that bug is, but we don't need two bugs for table-cell event floods.

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