Merge lp://staging/~themuso/libdbusmenu/violate-atk-docs-again into lp://staging/libdbusmenu/0.6
Proposed by
Luke Yelavich
Status: | Merged |
---|---|
Merged at revision: | 383 |
Proposed branch: | lp://staging/~themuso/libdbusmenu/violate-atk-docs-again |
Merge into: | lp://staging/libdbusmenu/0.6 |
Diff against target: |
17 lines (+5/-1) 1 file modified
libdbusmenu-gtk/client.c (+5/-1) |
To merge this branch: | bzr merge lp://staging/~themuso/libdbusmenu/violate-atk-docs-again |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Ted Gould (community) | Approve | ||
Luke Yelavich (community) | Abstain | ||
Review via email: mp+93525@code.staging.launchpad.net |
Description of the change
Do not set the accessible name to an empty string if the accessible_desc
property = NULL. Yes this was recently changed so that dbusmenu conformed
to Atk documentation, but the GTK menu item accessibility code does not yet
conform to sed documentation. As a result, all dbusmenu menu items that do not
have the accessible_desc property set end up getting an empty string for their
accessible name. In the long term, GTK accessibility needs to be fixed.
To post a comment you must log in.
On Fri, 2012-02-17 at 04:26 +0000, Luke Yelavich wrote:
> Do not set the accessible name to an empty string if the accessible_desc
> property = NULL. Yes this was recently changed so that dbusmenu conformed
> to Atk documentation, but the GTK menu item accessibility code does not yet
> conform to sed documentation. As a result, all dbusmenu menu items that do not
> have the accessible_desc property set end up getting an empty string for their
> accessible name. In the long term, GTK accessibility needs to be fixed.
Uhg, frustrating that's the case. Do you know of a link to a bug in the
GTK stack that we could put in a comment just to know why we did
this? :-)