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 670308 - Orca doesn't present anything when run dialog is launched
Orca doesn't present anything when run dialog is launched
Status: RESOLVED FIXED
Product: gnome-shell
Classification: Core
Component: general
unspecified
Other Linux
: Normal normal
: ---
Assigned To: gnome-shell-maint
gnome-shell-maint
Depends on: 667432
Blocks:
 
 
Reported: 2012-02-17 17:43 UTC by Alejandro Piñeiro Iglesias (IRC: infapi00)
Modified: 2012-03-10 01:31 UTC
See Also:
GNOME target: 3.4
GNOME version: 3.3/3.4


Attachments
a11y: accessible object for StEntry (4.44 KB, patch)
2012-02-17 17:52 UTC, Alejandro Piñeiro Iglesias (IRC: infapi00)
reviewed Details | Review
a11y: setting role and label actor for run dialog (1.65 KB, patch)
2012-02-17 17:53 UTC, Alejandro Piñeiro Iglesias (IRC: infapi00)
committed Details | Review
a11y: accessible object for StEntry (4.44 KB, patch)
2012-02-29 16:05 UTC, Alejandro Piñeiro Iglesias (IRC: infapi00)
committed Details | Review

Description Alejandro Piñeiro Iglesias (IRC: infapi00) 2012-02-17 17:43:30 UTC
STEPS TO REPRODUCE

1. Launch Orca
1.1 Accessibility icon (top panel at the right)
1.2 Press Universal Access Settings
1.3 Screen Reader On
2. Press Alt+F2
3. Run dialog appear

EXPECTED OUTCOME

Orca presents "Please enter a command" (dialog label) and "text" (role of the entry focused).

ACTUAL OUTCOME

Nothing is presented. But Orca present each individual key event

NOTES

The reason of this problem was that StEntry were not exposing his internal ClutterText. There was also some issues with the order of the events, already fixed on clutter itself. Patches will arrive soon.
Comment 1 Alejandro Piñeiro Iglesias (IRC: infapi00) 2012-02-17 17:52:47 UTC
Created attachment 207872 [details] [review]
a11y: accessible object for StEntry

I only have a doubt for this patch, due the long names I used the following code style for the type-related macros:

#define ST_ENTRY_ACCESSIBLE(obj) \
  (G_TYPE_CHECK_INSTANCE_CAST ((obj), \
  ST_TYPE_ENTRY_ACCESSIBLE, StEntryAccessible))

#define ST_IS_ENTRY_ACCESSIBLE(obj) \
  (G_TYPE_CHECK_INSTANCE_TYPE ((obj), \
  ST_TYPE_ENTRY_ACCESSIBLE))

#define ST_ENTRY_ACCESSIBLE_CLASS(klass) \
  (G_TYPE_CHECK_CLASS_CAST ((klass), \
  ST_TYPE_ENTRY_ACCESSIBLE, StEntryAccessibleClass))

#define ST_IS_ENTRY_ACCESSIBLE_CLASS(klass) \
  (G_TYPE_CHECK_CLASS_TYPE ((klass), \
  ST_TYPE_ENTRY_ACCESSIBLE))

#define ST_ENTRY_ACCESSIBLE_GET_CLASS(obj) \
  (G_TYPE_INSTANCE_GET_CLASS ((obj), \
  ST_TYPE_ENTRY_ACCESSIBLE, StEntryAccessibleClass))

I already used that style for StWidget. But on bug 668366 comment 3, Owen suggest that this style doesn't conform the used on other places. I used this style using as reference other classes like st-box-layout-child.h But is is true that other long-name-classed uses a one line style (like st-theme-node-transition.h, reaching a 139 line long)

Which style should I use?
Comment 2 Alejandro Piñeiro Iglesias (IRC: infapi00) 2012-02-17 17:53:20 UTC
Created attachment 207873 [details] [review]
a11y: setting role and label actor for run dialog
Comment 3 Alejandro Piñeiro Iglesias (IRC: infapi00) 2012-02-17 18:19:47 UTC
I forgot to mention: other example of requiring an accessible object for StEntry is the search entry at the overview.
Comment 4 Dan Winship 2012-02-28 18:02:52 UTC
Comment on attachment 207872 [details] [review]
a11y: accessible object for StEntry

code looks right. Just do what Owen says on the macro define style.
Comment 5 Dan Winship 2012-02-28 18:07:37 UTC
Comment on attachment 207873 [details] [review]
a11y: setting role and label actor for run dialog

looks good
Comment 6 Alejandro Piñeiro Iglesias (IRC: infapi00) 2012-02-29 16:05:04 UTC
Created attachment 208695 [details] [review]
a11y: accessible object for StEntry

(In reply to comment #4)
> (From update of attachment 207872 [details] [review])
> code looks right. Just do what Owen says on the macro define style.

I guess that this answer my question about if the correct style is the one used at st-theme-node-transition.h or the the one used at st-box-layout-child.h

Updated patch, using the style at st-theme-node-transition.h

Not committed yet as this bug depends on bug 667432.
Comment 7 Alejandro Piñeiro Iglesias (IRC: infapi00) 2012-03-10 01:31:02 UTC
(In reply to comment #6)

> Not committed yet as this bug depends on bug 667432.

Bug is not still fixed, but the patch related to this bug that allowed to set roles was committed, so the patches can be applied. Closing the bug as FIXED.