https://bugs.freedesktop.org/show_bug.cgi?id=39956
--- Comment #19 from Michael Meeks <[email protected]> --- > IN the context of implementing this final native UAA bridge for Windows, > eliminating? the JAB kludge, could we revisit enabling support for AT Tools > by default (gone the performance impact of the UAA <-> JAB <-> JRE JAA > performance hit)--and allow the individual ATs to manipulate NS > Accessibility, ATK AT-SPI, and MSAA/IAccessible2 as needed? Sure - so, ATK integration is already on by default if a11y is on by default [IIRC] - although that has some -hideous- performance impacts too IIRC, so maybe we vacillated on that; I'm not eager to see a 5+ second slower start for everyone to avoid a single a11y key ;-) [ and IIRC the GNOME guys decided to turn on a11y everywhere too and the decided against it ]. So my take is that - as long as it's not turned on on the desktop by default, it makes sense for us to enable by default as/when it's turned on globally. Either way - the state (as of when I last touched it) was that if Experimental mode is on, and IAcc2 is working - then we auto-enable it - and clobber the UI setting. Of course we should prolly yank out the UI setting in this case as well - but I was curious about the Mac situation. If (as I recall) Mac a11y is a bridge built-into the core/vcl then as/when we have IAcc2 working properly we should prolly just drop the JAva bridge, and the setting, and default it to on as/when anyone wants it ;-) Does that help ? =) -- You are receiving this mail because: You are the assignee for the bug.
_______________________________________________ Libreoffice-bugs mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
