Re: GNOME Accessibility on by default, and Firefox

[David Bolter <david bolter utoronto ca>]

Hi Aaron,

Replying to a message from Aaron which didn't have the lists cc'ed.

As Steve has brought up separately, this might indeed fit into the D-BUS
AT-SPI migration work. It doesn't seem terribly complex to add this
small thing that will have nice benefit (like what T.V. points out).

@Will Walker, we could maybe touch on this Monday night at 10 ;)

Are there any objections to all this?

cheers,
David

Aaron Leventhal wrote:
> In Firefox, there's a lot of code that doesn't need to run, and a lot
> of objects don't need to be created, when a11y isn't needed.
>
> Please, add lazy instantiation for accessibility. Would it fit to do
> this in the D-BUS AT-SPI migration project?
>
> - Aaron
>
>
> On 10/22/2008 8:35 PM, David Bolter wrote:
>> This is a common pattern. I hear it is also true for other things in FF
>> like dom mutation events.... only fire if there is a listener... makes a
>> lot of sense.
>>
>> A tree should only fall in the forest if someone is listening.<grin>
>>
>> D
>> Aaron Leventhal wrote:
>>   
>>> Mario, on Windows we use lazy instantiation. There is no need for an
>>> "enable a11y" flag in the OS. Just the fact that something asks us for
>>> an accessible object wakes us up. We get a WM_GETOBJECT event -- and
>>> before that a11y is not loaded.
>>>
>>> We really need lazy instantiation like that under Gnome. If the AT is
>>> loaded and starts asking us for objects, then we can wake up.
>>>
>>> - Aaron
>>>
>>>