Re: GNOME Accessibility on by default, and Firefox

BTW, I'm not sure about the details of what the Gecko
implementation does, but it would surprise me if it *always* loaded the
accessibility modules regardless of the gconf setting.
Afaik we do just use the gconf setting, which is the problem. Then we start creating accessible objects, firing extra events, doing extra processing for DOM mutations, lalala. What other check should we use before turning it on?

To be clear, if the gconf setting is not set, then no accessibility support will be enabled in Firefox. Is that right?

If so, I'm confused. By enabling accessibility, the user is saying they want accessibility enabled. But, it seems like the argument being made here is that even if the user enables accessibility, they really don't want it.

I think I might have missed the actual use case (I've been out of the country for the past week). Can you describe why someone would call to order pizza and then complain when it is delivered? Seems to me they should not have ordered it in the first place. ;-)

 > However, *something* needs to already be awake so that an assistive
> technology can discover the top level application object in the first > place.
Any time any app asks for even the root accessible object for a given window, that window receives a signal.

This may be the case on Windows, but I don't believe it is the case for GNOME.


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]