Plugins are not inserted in any hierarchy. If you want to know WHAT
(UI elements) is inserted and HOW your plugin can insert stuff (make
UI) in the hierarchy that's accessible, you RTFM! And if you did,
you'd know that whether it is in Safari.app or Bugaloo.app, or whether
it's inside the app itself or coming from a plugin DOES NOIT MATTER!
So of course the docs won't mention Safari plugins.
You're really looking at it from the wrong point, so you're still
asking the wrong questions. Cocoa accessibility is different from
Mozilla's. First LEARN how Cocoa accessibility is implemented and then
ASK YOURSELF how your code can make use of that.
You've provided me with information that I am still having trouble
finding in these docs -- namely that Safari plugins are not inserted
into the heirarchy, and therefore there probably isn't a strategy
for inserting OOP plugins into the accessible tree.
As browsers move more to muti-process architectures, including muti-
process content, I think it is worthwhile thinking through the right
places to solve the related issues so I'm looking to see what others
are doing. For example, native accessibility architectures tend to
be synchronous, but maybe we want to rethink that. I don't want to
go too off topic here though.
On 8/15/09 3:00 PM, Christiaan Hofman wrote:
On Aug 15, 2009, at 8:11 PM, David Bolter wrote:
Thanks for the link. Unfortunately I'm particularly interested in
how plugins are inserted into the heirarchy (if they are), and
especially how this is implemented for OOP plugins (probably
wrapping and remoting). I'll investigate.
Plugins are not inserted in the hierarchy. If you'd read these docs
you'd know that saying this doesn't even make sense. The docs tell
you WHAT is inserted and HOW. I advice you not to return until
you've read and understood these docs.
Does Safari have any plugin accessibility support?
If so, what about for out of process plugins?
If the answers aren't very useful that's because you're asking
the wrong questions (just a friendly advice, the docs have all
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