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 442578 - Dead children in Accerciser's plugin tabs
Dead children in Accerciser's plugin tabs
Status: RESOLVED OBSOLETE
Product: gtk+
Classification: Platform
Component: Accessibility
unspecified
Other Linux
: Normal normal
: ---
Assigned To: gtk-bugs
gtk-bugs
Depends on:
Blocks: 423930
 
 
Reported: 2007-05-31 12:27 UTC by Eitan Isaacson
Modified: 2018-04-15 00:34 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Test script (547 bytes, text/x-python)
2007-05-31 12:33 UTC, Eitan Isaacson
  Details
Proposed fix (670 bytes, patch)
2007-06-17 13:10 UTC, Eitan Isaacson
none Details | Review
Fixes tab naming issues (515 bytes, patch)
2007-06-26 19:15 UTC, Eitan Isaacson
none Details | Review

Description Eitan Isaacson 2007-05-31 12:27:53 UTC
I would write a simplified example of the bug, but I can't reproduce it outside of Accercier. In earlier versions of either gail or Accerciser, the plugin tab label's text interface would return the wrong string in getText. See bug 423930.
Lately is teems that some of the tab list's children show up dead.
Comment 1 Eitan Isaacson 2007-05-31 12:33:06 UTC
Created attachment 89101 [details]
Test script

First start accerciser, and run this in a seperate terminal.
Some of the page tab list's page tabs show up as None. This is not good.
Comment 2 Eitan Isaacson 2007-06-17 10:20:10 UTC
The problem with dead children has been worked around in Accerciser.
Comment 3 Eitan Isaacson 2007-06-17 13:10:25 UTC
Created attachment 90139 [details] [review]
Proposed fix

This patch assures that the text in the accessible's itext is identical to the page tab's label.
Comment 4 Eitan Isaacson 2007-06-26 19:15:34 UTC
Created attachment 90696 [details] [review]
Fixes tab naming issues

Although I still can't explain exactly what is happening, this fixes the problem where it is at. It seems like between the initialization and the mapping the label widgets somehow get swapped.
Comment 5 Li Yuan 2007-08-17 06:11:33 UTC
Yi, please take a look at why label is different from widget in Eitan's patch.
Comment 6 Yi Jin 2007-08-23 09:48:09 UTC
No matter how many tabs did I set to bottom panel, the output of that script is always:

[page tab | IPython Console]
   [scroll pane | ]
[page tab | Plugin Errors]
   [scroll pane | ]

If I set View->SinglePluginsView true, the script does not work. 

I use orca to test accerciser's tab page directly, and it always speak out the proper tab 's label. 

Comment 7 LiYan.Zhang 2008-01-04 10:00:54 UTC
(In reply to comment #1)
> 
> First start accerciser, and run this in a seperate terminal.
> Some of the page tab list's page tabs show up as None. This is not good.
> 

I made some modifications to the test script(accerciser_tab_bug.py), just as follows:

-bottom_pluginview = app_acc[0][0][1][1][0]
-top_pluginview = app_acc[0][0][1][0][1][0]
+bottom_pluginview = app_acc[0][0][1][1]
+top_pluginview = app_acc[0][0][1][0][1]

And then, running the new test script, I got the following result:

[page tab list | ]
   [page tab | IPython Console]
   [page tab | Interface Viewer]
   [page tab | Event Monitor]
[page tab list | ]
   [page tab | Plugin Errors]
   [page tab | API Browser]
   [page tab | Script Recorder]

Could you please show me your results running the test script? 
Thank you very much! 
Comment 8 Matthias Clasen 2018-02-10 05:25:34 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 9 Matthias Clasen 2018-04-15 00:34:47 UTC
As announced a while ago, we are migrating to gitlab, and bugs that haven't seen activity in the last year or so will be not be migrated, but closed out in bugzilla.

If this bug is still relevant to you, you can open a new issue describing the symptoms and how to reproduce it with gtk 3.22.x or master in gitlab:

https://gitlab.gnome.org/GNOME/gtk/issues/new