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 139474 - No accessibility implementation for NautilusCellRendererPixbufEmblem
No accessibility implementation for NautilusCellRendererPixbufEmblem
Status: RESOLVED OBSOLETE
Product: nautilus
Classification: Core
Component: Views: List View
2.24.x
Other All
: Normal normal
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
AP3
Depends on:
Blocks:
 
 
Reported: 2004-04-08 13:30 UTC by padraig.obriain
Modified: 2010-11-26 11:44 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description padraig.obriain 2004-04-08 13:30:28 UTC 
In nautilus list view the file or directory icon is in a
NautilusCellRendererPixbufEmblem. No accessible information can be obtained from
it.
Comment 1 Calum Benson 2004-10-21 16:49:14 UTC 
Apologies for spam-- ensuring Sun a11y team are cc'ed on all current a11y bugs.
 Filter on "SUN A11Y SPAM" to ignore.
Comment 2 Emmanuel Fleury 2008-11-10 14:42:59 UTC 
Is it still an active issue ?

I don't understand quite well what is the problem here. Could you elaborate ?
I guess it has something to do with the scope of NautilusCellRendererPixbufEmblem. Is it ?
Comment 3 Cosimo Cecchi 2008-11-10 20:38:04 UTC 
The problem is that NautilusCellRendererPixbufEmblem doesn't expose accessibility information, but maybe this might be solved by removing NautilusCellRendererPixbufEmblem completely and using the GEmblemedIcon facilities.
Comment 4 Allan Day 2010-06-20 18:54:13 UTC 
Changing component.
Comment 5 Cosimo Cecchi 2010-11-26 11:44:05 UTC 
(In reply to comment #3)
> The problem is that NautilusCellRendererPixbufEmblem doesn't expose
> accessibility information, but maybe this might be solved by removing
> NautilusCellRendererPixbufEmblem completely and using the GEmblemedIcon
> facilities.

That's exactly what we ended up doing, so this can be safely closed now.