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 644393 - Remove reference to document:content-changed signal from pyatspi contstants
Remove reference to document:content-changed signal from pyatspi contstants
Product: pyatspi2
Classification: Applications
Component: general
Other Linux
: Normal normal
: ---
Assigned To: Mike Gorse
pyatspi2 maintainer(s)
Depends on:
Blocks: 638537
Reported: 2011-03-10 14:12 UTC by Fernando Herrera
Modified: 2015-02-27 16:40 UTC
See Also:
GNOME target: ---
GNOME version: ---

Description Fernando Herrera 2011-03-10 14:12:07 UTC
There is a reference to that event on pyatspi constants, but neither atk nor at-spi includes it. Would it be nice to have it?
Comment 1 Alejandro Piñeiro Iglesias (IRC: infapi00) 2011-05-11 09:22:05 UTC
ATK Hackfest 2011 Conclusion:
 * Although it seems that it would be good to have that high level signal, it also seems that it would be hard to define when and how emit that signal.
 * So, unless a good new proposal appears, the plan it is not add this signal.
 * In the same way, as we are not going to add it, it would be good to remove that reference from pyatspi constants, in order to maintain coherence.

(In summary, now this bug is more about clean that reference that adding that signal).
Comment 2 Joanmarie Diggs (IRC: joanie) 2011-05-28 22:04:31 UTC
Mike, this is (I assume) an easy removal. Hope you don't mind me adding it to your to-do list so I can remove it from the 'needs assigning' and 'needs doing' lists from the ATK hackfest.

Thanks in advance!
Comment 3 Mike Gorse 2011-06-23 21:22:11 UTC
Removed in HEAD: 44739a
Comment 4 André Klapper 2015-02-27 16:40:55 UTC
[Moving at-spi/pyatspi2 bugs to separate product. See bug 740075]