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 580452 - Focused state (for menuitems) showing when it shouldn't, and lacking when it should show
Focused state (for menuitems) showing when it shouldn't, and lacking when it ...
Status: RESOLVED DUPLICATE of bug 711397
Product: gtk+
Classification: Platform
Component: Accessibility
2.12.x
Other All
: Normal normal
: ---
Assigned To: gtk-bugs
gtk-bugs
Depends on:
Blocks:
 
 
Reported: 2009-04-27 14:55 UTC by Andrés G. Aragoneses (IRC: knocte)
Modified: 2018-02-10 16:27 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Andrés G. Aragoneses (IRC: knocte) 2009-04-27 14:55:06 UTC
Please describe the problem:
It seems the FOCUSED state in menuitems is incorrectly implemented.

Steps to reproduce:
1. Open gedit.
2. Open accerciser.
3. On accerciser, select the "Select all" menuitem element on the hierarchy pane, and open the "Accessible" interface to see the states (Focused is not on the list, perfect).
4. Click on the Edit menu of Gedit, and hover to "Select All".
5. Hover the mouse now to the next item (Insert Date and Time...).


Actual results:
On step 4: Selected state is raised only.
On step 5: Focused state is raised.

Expected results:
On step 4: Selected *and* Focused states are raised.
On step 5: Both selected *and* Focused states are removed.

Does this happen every time?
Yes.

Other information:
Comment 1 Matthias Clasen 2018-02-10 05:24:41 UTC
We're moving to gitlab! As part of this move, we are moving bugs to NEEDINFO if they haven't seen activity in more than a year. If this issue is still important to you and still relevant with GTK+ 3.22 or master, please reopen it and we will migrate it to gitlab.
Comment 2 Joanmarie Diggs (IRC: joanie) 2018-02-10 16:27:05 UTC

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