https://bugs.documentfoundation.org/show_bug.cgi?id=168409
Michael Weghorn <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |NOTABUG --- Comment #4 from Michael Weghorn <[email protected]> --- (In reply to Jean-Pierre Ledure from comment #0) > accessiblecontext = element.RealInterface.AccessibleContext > ' > com.sun.star.accessibility.XAccessibleContext > [...] > > The > accessiblecontext.AccessibleChildCount > value is identical with the > settings.Count > property. Please note that the accessibility UNO API is unpublished and for LibreOffice-internal use only and subject to change by design. It is not meant to be used by third party code like macros or extensions, so anything that relies on it never had any guarantee to keep working. Quoting from the commit message of f82aac71ede9c3f2dc059ca4c8b24f60e0841933 - the commit mentioned in comment 2: > According to the discussion in [1], there might be third-party > code (unrelated to a11y except for using UNO a11y API) also > relying on the assumption that the vcl::Window's XAccessible > is its VCLXWindow, but the UNO a11y API is an internal > implementation detail explicitly unpublished in > > commit 70626249cd247d9acdad417b8eaf252bae22c059 > Date: Thu Nov 29 00:27:03 2012 +0100 > > API CHANGE a11y unpublishing and add/removeListener rename. > > and has no stability guarantuee whatsoever and is therefore > not meant to be used by external users. If any third-party > code was relying on this implementation detail, it should be > ported away from relying on UNO a11y API. I'm sorry to say that, but this is an intentional change in the context of refactoring accessibility code to better fulfill it's actual purpose (support assistive technology via the platform accessibility protocols) and increase code maintainability. Please try to find an alternative to using the UNO accessibility API - and feel free to create a new feature request (with clear requirements + use case) in case you're missing specific API. -- You are receiving this mail because: You are the assignee for the bug.
