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 127400 - SPI_STATE_FOCUSED is missing for some objects
SPI_STATE_FOCUSED is missing for some objects
Status: VERIFIED INCOMPLETE
Product: atk
Classification: Platform
Component: gail
git master
Other Linux
: Normal normal
: ---
Assigned To: padraig.obriain
padraig.obriain
Depends on:
Blocks: 127890
 
 
Reported: 2003-11-19 15:38 UTC by remus draica
Modified: 2009-08-15 18:40 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Proposed patch (3.33 KB, patch)
2003-11-26 10:02 UTC, padraig.obriain
none Details | Review

Description remus draica 2003-11-19 15:38:59 UTC
In case of focus: event, the state for the object doesn't contain
SPI_STATE_FOCUSED. 

From my checks I saw that for menu, menu-item, radio-menu-item,
check-menu-item, page-tab (all with gedit) and for text (with yelp).
Comment 1 padraig.obriain 2003-11-19 15:58:02 UTC
Is this a bug? 

For the menus and menu items and page tab the state SELECTED should be
set.
Comment 2 bill.haneman 2003-11-19 21:19:09 UTC
OK, so we could test for SELECTED || FOCUSSED...

but it does seem to me that if an object emits "focus:" it would be
reasonable for its state to include FOCUSSED.
Comment 3 korn 2003-11-19 21:33:54 UTC
In the case of Java, selection change events are fired, not focus.  I 
believe the bridge re-casts them.
Comment 4 bill.haneman 2003-11-25 15:20:37 UTC
I still believe that objects which emit 'focus:' ought to be FOCUSSED.

In the meantime gnopernicus can check for FOCUSSED || SELECTED, to
work around the user-visible problem.
Comment 5 korn 2003-11-25 17:45:27 UTC
I don't disagree with the statement "objects that emit focus shouldn't
be focused".  Rather, I'm pointing out that from the get go Java never
fired focus events for this; the gnome-java-bridge did the mapping. 
This suggests that the gnome-java-bridge should map the
AccessibleStateSet "selected" in menus to "focused".
Comment 6 bill.haneman 2003-11-25 18:15:53 UTC
yes, for Java apps this will need to be handled in the java bridge.
But for gtk+ apps this will have to be mapped for the various gail
widgets as well which emit 'focus' but don't actually technically have
gtk+ focus, for instance table cells and menu items. 

Comment 7 padraig.obriain 2003-11-26 10:02:21 UTC
Created attachment 21823 [details] [review]
Proposed patch
Comment 8 padraig.obriain 2003-11-26 10:04:20 UTC
The proposed patch ensure that the focus object has state FOCUSED.
This should fix the problem for ATK. A similar fix will need to be
made in the Java Access Bridge.
Comment 9 padraig.obriain 2003-11-26 17:12:28 UTC
Patch committed to CVS HEAD.
Comment 10 Dana Ormenisan 2004-02-10 15:34:09 UTC
 In Character Map application the state for the combobox 'Font Family'
doesn't contain SPI_STATE_FOCUSED.
Comment 11 padraig.obriain 2004-02-10 15:57:54 UTC
What is the Character Map application? How do I start it?
Comment 12 Dana Ormenisan 2004-02-10 16:28:41 UTC
Applications --> Accessories --> Character Map or launch 'charmap'
Comment 13 padraig.obriain 2004-02-10 17:26:08 UTC
The text entry object which is a child of the combo-box has state
FOCUSED.

Do we need to set state FOCUSED on the combo-box object as well?
Comment 14 padraig.obriain 2004-02-10 17:32:20 UTC
I have looked again and when the combo-box is reported as the focus
object it does have state FOCUSED set.
Comment 15 padraig.obriain 2004-02-16 15:34:35 UTC
Any further information on this. It looks correct to me.
Comment 16 padraig.obriain 2004-02-19 10:13:53 UTC
I am closing this bug as I have received no reponse.

Please reopen if you can confirm that the problem still occurs.
Comment 17 padraig.obriain 2004-03-09 08:35:24 UTC
*** Bug 122713 has been marked as a duplicate of this bug. ***
Comment 18 david.hawthorne 2004-03-25 15:35:59 UTC
This bug(stemming from 122713) is still occuring on my machine with gnome from
CVS HEAD 22 Mar.