Hey Jason.
> I don't know what you're proposing and I am not well qualified to give an
> opinion on whether your feature should be written in Orca or in LibreOffice.
> Rather, I am expressing a general concern about the push for more and more
> complex, application-specific, interactive features i
Hi Dattatray,
In addition to Jason's comments below, I'd like to weigh in from a
historical perspective...
Many years ago, we decided to only expose Accessibles for the
visible content in OOo because of the huge memory hit doing
otherwise would involve for a
Dattatray Bhat wrote:
> Thanks for the prompt response. I am working on Orca screen reader. I want
> to add a feature that would provide the user with a document summary
> including all elements (headings, tables, form elements etc.) irrespective
> of whether they are on-screen or off-screen.
I
On Tue, Apr 17, 2012 at 11:54 AM, Jason White wrote:
> Dattatray Bhat wrote:
>
> > Thus at-spi holds information only for those document elements which are
> > visible on the screen. Can anybody please suggest a way to access the
> > document elements which have moved out of the screen?
>
> Why
Dattatray Bhat wrote:
> Thus at-spi holds information only for those document elements which are
> visible on the screen. Can anybody please suggest a way to access the
> document elements which have moved out of the screen?
Why do you want to do this?
Presumably your accessibility application
