https://bugs.documentfoundation.org/show_bug.cgi?id=173006

Michael Weghorn <[email protected]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|---                         |NOTABUG
           See Also|                            |https://bugs.documentfounda
                   |                            |tion.org/show_bug.cgi?id=16
                   |                            |8409

--- Comment #5 from Michael Weghorn <[email protected]> ---
(In reply to Neil Roberts from comment #2)
> You might be able to fix it if you do this instead:
> 
> StarDesktop.CurrentComponent.CurrentController.Frame.ContainerWindow.
> getProperty("XAccessible").AccessibleContext
> 
> That was what was done to fix AcceleratorKeyChecker.fodt.
> 
> https://gerrit.libreoffice.org/c/core/+/208207

Indeed, that can be a temporary workaround.

> But in the long run the XAccessible interface is still meant to be an
> internal unpublished interface that can change between releases so we should
> probably think of an alternative if people want to use it from macros.

Indeed. Please notice that the accessibility UNO API is meant for
LibreOffice-internal purposes only, in order to implement/provide support for
assistive technology.

Since the API can change at any point in time by design, using it in third
party code (macros or extensions) is at your own risk and can break, so (while
annoying for anything that is relying on it) this is technically not a bug.

If there are specific cases currently (mis)using the a11y API, they should
ideally be ported away from using it. (Adding new API where needed might be an
option.) But please keep in mind that relying on implementation details of the
vcl widgets (i.e. custom widgets implemented by LibreOffice) by itself can also
be problematic, since that only works when vcl widgets are actually used and
e.g. not for native GTK or Qt widgets. (See e.g. tdf#163988 for one example
currently using vcl widgets, but where porting to native widgets is suggested.)

tdf#168409 has some more background information/discussion.

-- 
You are receiving this mail because:
You are the assignee for the bug.

Reply via email to