Eitan, Aaron, gang,
One thing that strikes me about this, and about an earlier discussion
around IAcc2 relating to the Collection interface. As I understand it,
IAcc2 doesn't implement Collections because IAcc2 is in process and fast
and therefore doesn't need it. At the same time, in order to get all of
the info quickly from a web browser, we need to go with a DOM interface
(and one that is potentially unique to Firefox/Mozilla - will the same
DOM interface be easily implemented on WebKit? on an office suite?).
These two sentiments seem at odds to me, when part of the reason for
doing Collections was to have a very generalized way to get a document
content in a highly efficient fashion.
Regards,
Peter Korn
Accessibility Architect & Principal Engineer,
Sun Microsystems, Inc.
On Fri, 2008-09-26 at 14:24 +0200, Aaron Leventhal wrote:
My proposal is this:
Include at least ISimpleDOMNode, and possibly ISimpleDOMDocument and
ISimpleDOMText in IAccessible2, as optional interfaces for an
application to expose.
I think a concern is this being major departure from IA2/ATK
similarities. This could cause two ill effects:
1. Makes it harder to port future IA2 apps to AT-SPI.
2. Most ATs on Windows will use a radically different code path for
doing their stuff with Firefox, then their Unix brethren. This will
cause support for the two platforms to vary and not be consistent.
Again, as Aaron mentioned, ATs are already using ISimpleDom*. So maybe
point 2 is not very valid. But point 1 still stands, especially if these
interfaces are canonized in IA2.
my two pennies.
Eitan.
_______________________________________________
Accessibility-ia2 mailing list
[email protected]
https://lists.linux-foundation.org/mailman/listinfo/accessibility-ia2
_______________________________________________
Accessibility-ia2 mailing list
[email protected]
https://lists.linux-foundation.org/mailman/listinfo/accessibility-ia2
