26
edits
NPAPI:NativeAccessibility: Difference between revisions
Jump to navigation
Jump to search
Add OOP considerations
BradTaylor (talk | contribs) (Give example of a base accessible type) |
BradTaylor (talk | contribs) (Add OOP considerations) |
||
| Line 9: | Line 9: | ||
* '''Accessibility Toolkit (ATK)''' - the standard accessibility API on Linux. | * '''Accessibility Toolkit (ATK)''' - the standard accessibility API on Linux. | ||
* '''Document Object Model (DOM)''' - a in-memory tree representation of the content of a web page. | * '''Document Object Model (DOM)''' - a in-memory tree representation of the content of a web page. | ||
* '''Interprocess Communication (IPC)''' - a way of communicating betweenthread and process boundaries. | |||
= Related Approaches = | = Related Approaches = | ||
| Line 40: | Line 41: | ||
This accessible does not need to be updated, so the browser may cache the object for the life of the plugin. Plugins that need to regularly remove and re-add their root accessible object should return a container-type object from <tt>NPN_GetValue</tt> and make their root accessible a child of the container. | This accessible does not need to be updated, so the browser may cache the object for the life of the plugin. Plugins that need to regularly remove and re-add their root accessible object should return a container-type object from <tt>NPN_GetValue</tt> and make their root accessible a child of the container. | ||
= Implementation Recommendations = | |||
== Out-of-process Plugins == | |||
Since accessibility objects are living objects, they cannot be simply serialized over an IPC between the plugin process and the browser process. Instead, implementors should create proxy objects that wrap methods on the plugin's accessible, and remote the calls over IPC. | |||