Re: plugin accessibility
Re: plugin accessibility
- Subject: Re: plugin accessibility
- From: Michael Ash <email@hidden>
- Date: Sun, 16 Aug 2009 15:30:37 -0400
Before this discussion blows up any further I'd like to just clarify a
couple of things for David.
The main disconnect in this discussion, as far as I can see, is that
Accessibility has no concept of plugins. They are not within its field
of view. As far as the Accessibility API is concerned, the idea of a
"plugin" does not exist.
The trouble is that David keeps asking questions about how plugins
relate to Accessibility. Since they don't, others on the list are
getting kind of frustrated, but this fundamental sticking point
doesn't seem to be getting explained 100% adequately. (Not meant as
any sort of criticism, it's just the sort of thing that happens.)
To put it simply: anything relating to the actual plugin code or API
is your own problem, and unrelated to Accessibility. Once your plugin
is loaded and running, then it's just like any other code within the
app, and your interactions with Accessibility are *exactly* the same
as they would be if you were writing a regular application.
So, get your basic plugin stuff built, and make it go (something
you'll have to work with Mozilla on, since that's their end of
things), and then once you have a foundation running and need to
interact with Accessibility, ask Accessibility-specific questions
here. But you can leave the word "plugin" out of it entirely, because
it's just not relevant to the API.
Mike
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Accessibility-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden