<html> <head> <base href="https://bugs.documentfoundation.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - Should implemented scrollto, scrolltopoint, scrollsubstringto, scrollsubstringtopoint" href="https://bugs.documentfoundation.org/show_bug.cgi?id=118418#c9">Comment # 9</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - Should implemented scrollto, scrolltopoint, scrollsubstringto, scrollsubstringtopoint" href="https://bugs.documentfoundation.org/show_bug.cgi?id=118418">bug 118418</a> from <a class="email" href="mailto:samuel.thibault@ens-lyon.org" title="Samuel Thibault <samuel.thibault@ens-lyon.org>"> Samuel Thibault</a> <pre>Hello, Just to make it clear: I would say that before spending money on this issue, the real remaining needs should be assessed. Ideally we'd have scroll* support on all scrollable widgets of course, but in practice we don't really need it on all of them, far from it. In orca for instance, it is essentially used when requesting to speak a whole text. So it is really needed only on the document itself and in textview pieces of dialog boxes. The current support is already enough for various use cases, notably it works for the document. Before planning to invest money on completing the support for other widgets, I would say to first check which pieces of the interface the users are still lacking support for. Possibly the current support is already really fine, and it's better to prioritize other tasks. Restoring the accessibility tests comes to my mind as a high priority. Samuel</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>