Created attachment 44220 [details] Accerciser screen-shot: hyperlink exposes ROLE_PARAGRAPH, and no URL to AT-SPI. A hyperlink in Libre Office writer document doesn't expose the correct role and URL to AT-SPI. It exposes ROLE_PARAGRAPH and no URL. If it would expose the correct role (ROLE_LINK or some other appropriate role) and the URL, assistive tools like a screen reader can use the information to improve accessibility of the document. Steps to reproduce: 1. Start Libre Office writer. Create a new text document. Add a hyperlink with text 'http://www.libreoffice.org/', targeted to 'http://www.libreoffice.org/'. Save the document. 2. Start Accerciser accessibility explorer. 3. Go to the accessible tree view at top left. As shown in attached screen-shot, select the accessible object corresponding to the hyperlink just created. The Role column shows 'paragraph'. 4. In the plug-in view at top right, select Interface Viewer. The first line shows the role as 'paragraph'. The table under Hypertext shows the start and end offsets for the hyperlink text, but no URI. 5. Go to the IPythonConsole at bottom. acc.queryText().getText(0,27) returns text 'http://www.libreoffice.org/'. acc.getRole() returns ROLE_PARAGRAPH. acc.queryHypertext().getNLinks() returns 1, indicating one link. acc.queryHypertext().getLink(0) returns a Hyperlink object. acc.queryHypertext().getLink(0).nAnchors returns 1, indicating one anchor. acc.queryHypertext().getLink(0).getURI(0) returns '', not the URL.
[This is an automated message.] This bug was filed before the changes to Bugzilla on 2011-10-16. Thus it started right out as NEW without ever being explicitly confirmed. The bug is changed to state NEEDINFO for this reason. To move this bug from NEEDINFO back to NEW please check if the bug still persists with the 3.5.0 beta1 or beta2 prereleases. Details on how to test the 3.5.0 beta1 can be found at: http://wiki.documentfoundation.org/QA/BugHunting_Session_3.5.0.-1 more detail on this bulk operation: http://nabble.documentfoundation.org/RFC-Operation-Spamzilla-tp3607474p3607474.html
Today I rechecked my observation with Libre Office dev 3.5.0 beta2 and found that the bug persists. I suggest that the bug be moved back to NEW status.
Dear bug submitter! Due to the fact, that there are a lot of NEEDINFO bugs with no answer within the last six months, we close all of these bugs. To keep this message short, more infos are available @ https://wiki.documentfoundation.org/QA/NeedinfoClosure#Statement Thanks for understanding and hopefully updating your bug, so that everything is prepared for developers to fix your problem. Yours! Florian
I don't know how I missed the bugmail, but this was never addressed.
Okay
Corresponding Apache OpenOffice bug: https://issues.apache.org/ooo/show_bug.cgi?id=117206
I'm taking this, the solution can be related to bug #35105
Actually, links don't work like that. The paragraph should still have the ATK_PARAGRAPH role, and it has a hypertext interface through which we would be able to query the hyperlinks contained in that paragraph. It can be checked from accerciser in the interface viewer tab or with acc.queryHypertext() from the IPython console. Anyway, there is still a bug; in 4.3 (master) there is no information about hyperlinks at all in that interface. In an older version, 4.1.4, it does, although some fields are missing (Uri fields seems to be so).
Some facts about hyperlinks in master after further investigation: * It does expose the hyperlinks throught the hypertext interface correctly. * Hyperlink objects got through that interface contain proper start and end positions and Uri. * Hyperlink objects got through that interface do not implement get_object properly.
The implementation of hyper_link_get_object [1] is incorrect; it should return the associated ATK object, according to ATK docs [2], but it actually gets a string with the destination URL, tries to transform it into an accessible object, crashes in that transformation and returns nothing. To fix the problem it looks like we should call XAccessibleHyperlink::getAccessibleActionAnchor instead of XAccessibleHyperlink::getAccessibleActionObject from hyper_link_get_object, but there is also a problem here; getAccessibleActionAnchor may also return a string according to the docs [3], which cannot be transformed into an accessible object either. We have to think a bit how the implementation of hyper_link_get_object should be. What does 'the associated ATK object' mean? The paragraph that contains the hyperlink, the text chunk with the link...? [1] http://opengrok.libreoffice.org/xref/core/vcl/unx/gtk/a11y/atkhypertext.cxx#73 [2] https://developer.gnome.org/atk/unstable/AtkHyperlink.html#atk-hyperlink-get-object [3] http://api.libreoffice.org/docs/idl/ref/interfacecom_1_1sun_1_1star_1_1accessibility_1_1XAccessibleHyperlink.html#a293f7cf73fb1030059aa993133726d53
In a conversation with the maintainer of ATK, he pointed out that we are missing one piece in this puzzle, which is AtkHyperlinkImpl [1] type. The paragraph should have a set of children of this type, one for each hyperlink, and at the same time the AtkHyperlink objects returned through the AtkHypertext interface of the paragraph should return the corresponding AtkHyperlinkImpl object in their implementation of get_object. [1] https://developer.gnome.org/atk/unstable/atk-AtkHyperlinkImpl.html
Dear Jacobo Aragunde Pérez, This bug has been in ASSIGNED status for more than 3 months without any activity. Resetting it to NEW. Please assigned it back to yourself if you're still working on this.
** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Dear Dattatray Bhat, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Dear Dattatray Bhat, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug