https://bugs.documentfoundation.org/show_bug.cgi?id=168409
Jean-Pierre Ledure <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|NOTABUG |--- Status|RESOLVED |REOPENED --- Comment #8 from Jean-Pierre Ledure <[email protected]> --- (In reply to Michael Weghorn from comment #6) > In general, any API that is not marked as "published" is unpublished and > considered for internal use. > See also tdf#163747 for more details. > Unfortunately, the distinction apparently hasn't been clear to many users of > the API in practice. Indeed, new for me. > (We generally try to avoid changing even unpublished > API "for no reason" if there is a fair chance of it being used in practice, > but I don't see keeping UNO a11y API as something feasible going forward. > Those uses of the API I have become aware of so far were actually unrelated > to the intention of the API, i.e. not directly related to accessibility in > the first place.) I was curious and typed 'AccessibleContext' in the search box of https://forum.openoffice.org/en/forum/viewforum.php?f=19 => 109 matches ... > ... > But please be aware that this can only be seen as a temporary workaround, as > that would still rely on accessibility implementation details that are > subject to further changes in the future. > > As far as I can see, this commit is also not included in the 25-8 branch, > but if such a temporary workaround is desirable for now to give more time > for finding a better solution, making that approach available for 25.8 as > well could be investigated. First on master, afterwards, if successful, application on 25.8. > > What do you think? 1. I'm sure that, after your commits, the LO code is now better prepared for the future, but ... 2. A standard feature of LO is deeply broken: (https://help.libreoffice.org/latest/en-US/text/sbasic/shared/03/sf_toolbarbutton.html?DbPAR=BASIC). The subcomponents of a toolbar cannot be read anymore with the so far used [UNO] interfaces. => A sustainable alternative should be found. 3. I reset the status of this bug report. 4. Thanks for your support ! -- You are receiving this mail because: You are the assignee for the bug.
