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 721045 - The accessible role of GtkColorSwatch should not be ATK_ROLE_UNKNOWN
The accessible role of GtkColorSwatch should not be ATK_ROLE_UNKNOWN
Status: RESOLVED FIXED
Product: gtk+
Classification: Platform
Component: Accessibility
3.10.x
Other Linux
: Normal normal
: ---
Assigned To: gtk-bugs
gtk-bugs
Depends on:
Blocks: 721048
 
 
Reported: 2013-12-25 21:45 UTC by Joanmarie Diggs (IRC: joanie)
Modified: 2014-01-04 23:53 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Joanmarie Diggs (IRC: joanie) 2013-12-25 21:45:21 UTC
$ python3

>>> from gi.repository import Gtk
>>> chooser = Gtk.ColorChooserWidget()
>>> box = chooser.get_children()[0]
>>> grid = box.get_children()[0]
>>> swatch = grid.get_children()[0]
>>> acc = swatch.get_accessible()
>>> acc.get_description()
'Dark Aluminum 2'
>>> acc.get_role()
<enum ATK_ROLE_UNKNOWN of type AtkRole>

As for what the role should be instead.... ATK doesn't have role specific for this particular type of widget. We could certainly add one if need be. Alternatively, since functionally this widget seems to behave like a radio button perhaps ATK_ROLE_RADIO_BUTTON could be used?

Thoughts?
Comment 1 Alejandro Piñeiro Iglesias (IRC: infapi00) 2013-12-26 15:22:58 UTC
(In reply to comment #0)

> As for what the role should be instead.... ATK doesn't have role specific for
> this particular type of widget. We could certainly add one if need be.
> Alternatively, since functionally this widget seems to behave like a radio
> button perhaps ATK_ROLE_RADIO_BUTTON could be used?
> 
> Thoughts?

I agree with using ATK_ROLE_RADIO_BUTTON. Any other option would be define a new role just for that widget, and that sounds like an overkill to me.