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 720123 - EXTENDED roles should not be supported anymore
EXTENDED roles should not be supported anymore
Status: RESOLVED FIXED
Product: at-spi
Classification: Platform
Component: at-spi2-core
unspecified
Other Linux
: Normal normal
: ---
Assigned To: At-spi maintainer(s)
At-spi maintainer(s)
Depends on: 720117
Blocks:
 
 
Reported: 2013-12-09 18:27 UTC by Alejandro Piñeiro Iglesias (IRC: infapi00)
Modified: 2017-10-23 10:19 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Deprecate ATSPI_ROLE_EXTENDED (1.10 KB, patch)
2013-12-09 18:28 UTC, Alejandro Piñeiro Iglesias (IRC: infapi00)
none Details | Review
Deprecate ATSPI_ROLE_EXTENDED (1.07 KB, patch)
2017-01-09 16:24 UTC, Alejandro Piñeiro Iglesias (IRC: infapi00)
committed Details | Review

Description Alejandro Piñeiro Iglesias (IRC: infapi00) 2013-12-09 18:27:19 UTC
Something that we have been debating for a long time have happened. ATK has deprecated atk_role_register (bug 720117). That means that an ATK toolkit/application shouldn't register a new role. This change should be expanded to at-spi2-core, at-spi2-atk and pyatspi2.
Comment 1 Alejandro Piñeiro Iglesias (IRC: infapi00) 2013-12-09 18:28:53 UTC
Created attachment 263833 [details] [review]
Deprecate ATSPI_ROLE_EXTENDED
Comment 2 Alejandro Piñeiro Iglesias (IRC: infapi00) 2013-12-09 18:34:08 UTC
Now asking about opinions: with the previous commit we are just saying that that state is deprecated, but not removing the internal support on at-spi2-atk, at-spi2-core and atk. That means that we are encouraging to not use extended roles anymore, but if an application use register, it will still "arrive" to applications using pyatspi2. This is the conservative approach, and will give some time to apps to adapt to this change.

But we could be more aggressive:
 * Not removing the public methods, in order to not break API/ABI
 * But remove internal management of extended roles.
 * That would mean that applications could use those methods (as the API is still there), but those roles will not be available to pyatspi2 applications.

This would mean that applications would need "to hurry" as some breakage would appear. But that seems too aggressive to me.

So for anyone reading this comment. Opinions?
Comment 3 Joanmarie Diggs (IRC: joanie) 2013-12-09 18:47:33 UTC
(In reply to comment #2)
> So for anyone reading this comment. Opinions?

Orca right now encounters an extended role from LibreOffice Calc and needs to be able to identify this beast (the "input line") in some cases to present it; in other cases to ignore it. So I'm leaning towards the less aggressive approach and the hopes that they'll be bugged enough by the deprecation warnings from ATK. :) Once LibreOffice is free of ROLE_EXTENDED, I think we can be more aggressive.

The other guilty party, if memory serves me, is evolution. At the moment, their accessibility support is so completely and utterly broken that the aggressive approach won't make a hill of beans of difference.
Comment 4 Alejandro Piñeiro Iglesias (IRC: infapi00) 2017-01-09 16:24:53 UTC
Created attachment 343165 [details] [review]
Deprecate ATSPI_ROLE_EXTENDED

Previous patch wrongly marked as deprecated ATSPI_RELATION_EXTENDED instead of ATSPI_ROLE_EXTENDED. It is likely that that one should be deprecated too, but that is a topic for a different bug.
Comment 5 Mike Gorse 2017-01-19 16:34:48 UTC
Comment on attachment 343165 [details] [review]
Deprecate ATSPI_ROLE_EXTENDED

Committed and added to 3.23.4.
Comment 6 Peter Vágner 2017-10-23 10:11:57 UTC
This should get closed shouldn't it?
Comment 7 Alejandro Piñeiro Iglesias (IRC: infapi00) 2017-10-23 10:19:57 UTC
(In reply to Peter Vagner from comment #6)
> This should get closed shouldn't it?

Yes, I think so. Thanks.