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.
Status: RESOLVED DUPLICATE of bug 690004
Product: at-spi
Classification: Platform
Component: at-spi2-core
Other All
: Normal normal
: ---
Assigned To: At-spi maintainer(s)
At-spi maintainer(s)
Depends on: 665598
Blocks: 638537
Reported: 2011-12-05 15:55 UTC by Joanmarie Diggs (IRC: joanie)
Modified: 2017-06-16 22:25 UTC
See Also:
GNOME target: ---
GNOME version: ---

Description Joanmarie Diggs (IRC: joanie) 2011-12-05 15:55:47 UTC
(Once we have ATK_STATE_READ_ONLY, we'll need it in AT-SPI for ATs.)

+++ This bug was initially created as a clone of Bug #665598 +++

The definition of ATK_STATE_EDITABLE is: "Indicates the user can change the contents of this object." This clearly addresses text widgets. However, whether or not it also applies to widgets which:

* are enabled
* are sensitive
* are focusable
* have a usually-changeable state
* presently lack the ability to change the state

Consider, for example, cb4 on this page [1]. The checkbox is for all intents and purposes a normal checkbox, however the user is prevented from changing its state.

If we agree that 'state' != 'contents', then ATK_STATE_EDITABLE (or the lack thereof) would not be a means to communicate the present read-only condition of this checkbox (and other widgets like it). In this case, a new ATK state would be needed.

If, on the other hand, the conclusion is that 'state' == 'contents', then every widget whose contents (including state) could be altered by the user would need to have ATK_STATE_EDITABLE added to it. This would involve quite a few widgets and multiple toolkits: quite a lot of work given how rare things like the read-only dojo checkbox happen to be. Therefore, a new ATK state would be preferable.

For this reason, I am proposing the creation of ATK_STATE_READ_ONLY.

The addition of this state would raise the question of what to do about read-only text widgets. Should STATE_EDITABLE be removed and ATK_STATE_READ_ONLY be added? Or something else? I personally think this is less of a concern. But FWIW, we could deprecate STATE_EDITABLE and make the new read-only state apply to all widgets.

Comment 1 André Klapper 2012-02-26 10:43:32 UTC
[Resetting QA Contact to newly introduced "at-spi-maint@gnome.bugs". 
Reason: So far it was impossible to watch changes in at-spi bug reports without following all the specific persons (Li Yuan, Bill Haneman, Jeff Wai, ...) and also their activity outside of at-spi reports.

IMPORTANT: Anyone interested in following all bug activity (including all maintainers) must watch the "at-spi-maint@gnome.bugs" dummy user by adding it to the 'Users to watch' list under Preferences->Email preferences. This is also the default procedure nowadays in GNOME when setting up new products.]
Comment 2 André Klapper 2013-08-14 10:06:33 UTC
[Mass-resetting default assignee, see bug 705890. Please reclaim this bug report by setting the assignee to yourself if you still plan to work on this. Thanks!]
Comment 3 Joanmarie Diggs (IRC: joanie) 2017-06-16 22:25:12 UTC

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