Electrolysis/Meetings/2009-08-14-plugins

2009-08-14: Meeting to discuss Accessibility+Plugins

Attending:

• davidb
• brad
• bsmedberg
• jst
• josh

Proposal by Novell: https://wiki.mozilla.org/Plugins:NativeAccessibility (making Moonlight accessible)

• Patch is available, adding an NPAPI NPP_GetValue method, passing NPNVNativeAccessible

• bsmedberg> Concern about ATK: is it binary/API compatible across versions? answer: yes, seemingly so

• bsmedberg> it may be better for for the enumeration to be toolkit-specific enumeration value e.g. NPNVNativeAccessibleATK

• brad> Writing a remoting layer for ATK may not be too large a task: the API involves a few basic types:
  • http://library.gnome.org/devel/atk/unstable/AtkObject.html
  • http://library.gnome.org/devel/atk/unstable/AtkStateSet.html
  • http://library.gnome.org/devel/atk/unstable/AtkText.html#AtkAttributeSet
  • http://library.gnome.org/devel/atk/unstable/AtkRelationSet.html

• brad> It may also be possible to move this remoting into the atk-bridge itself
• bsmedberg> kinda like atk_plug_new/atk_plug_connect

• bsmedberg> Who are the atk-bridge/AT-SPI maintainers? Are they going to be open to the atk_plug idea?

• bsmedberg> So if we have support in the atk-bridge (preferred) or can write our own remoting layer (ugh), I think this is ok.

• jst> What's the status on mac? Safari already does OOP plugins in some cases?
• davidb> I don't think they have plugin accessibility now, but I'm not sure.

• jst> If it's possible to have multiple accessibility frameworks, we should try to make sure the NPP_GetValue enumeration specifies the toolkit and isn't generic... or that there's some way to query the plugin or host for the preferred accessibility toolkit.

• jst> Since there is a patch already available, I think we can consider taking it now and get it in for 1.9.2... although it can't wait long!
  • josh to review