https://bugs.documentfoundation.org/show_bug.cgi?id=168409
--- Comment #20 from Michael Weghorn <[email protected]> --- (In reply to Xisco Faulí from comment #18) > Hi Michael, > I'm not aware of anything else using the UITest API other than the UItests > themself. > Your change in https://gerrit.libreoffice.org/c/core/+/191456 makes sense to > me and if merged, I don't think it's going to change in the future, so at > least it's going to be stable on that regard > Regarding your question about whether using the UITest API from ScriptForge, > I'm afraid I can't answer it... I'm not sure whether this is the best > approach or if other approaches are desirable. @Xisco: Thanks for the feedback! If you're not explicitly advising against using the UITest API, then I think that it is at least a better alternative than using the a11y API if ScriptForge wants to continue accessing VCL implementation details for now. (In reply to Jean-Pierre Ledure from comment #19) > > One option could also be to implement the solution from comment#13 right > > away for master and 25-8, then switch to the UITest API based solution for > > master only once it's ready, without the need for it to be finished before > > the next 25.8 release. > > +1 Great, that sounds like we have a plan for the steps to take then. @Jean-Pierre: Could you please check whether https://gerrit.libreoffice.org/c/core/+/191456 is all you need to switch from a11y API to the new approach or if anything else is missing? (whenever you get to it) -- You are receiving this mail because: You are the assignee for the bug.
