Created attachment 108828 [details] Example Document Calc seems to have a strange behaviour when using multiple links in a single cell. I tried this solution to generate a sort of clickable index in a large spreadsheet. If the alignment is "left", the index works fine, each link is connected to its area. If the alignment is "center" or "right", all the links in the cell result identical to the first one. This happens both using manual formatting or cell styles. The problem seems to be easily reproducible. I attach an example document. Note that OpenOffice has the same problem and MS Office don’t allow multiple links in a single cell. Supposedly the bug afflicts all the versions of Libreoffice Calc.
Thank you, Calabar, for helping us to improve LibreOffice. The spreadsheet you attached illustrates your problem very clearly; it sets an example for me to follow in my own bug reports. I observe the problematic behaviour on Windows in a daily build (2014-11-02), and on Linux in the daily dbgutil bibisect repo version 2014-11-03 and in the 43all bibisect repo version oldest. This report is similar to bug 48803 in that the behaviour of a hyperlink depends on the alignment of text in the cell, but I am not quite ready to mark that one as a duplicate: (1) Bug 48803 reports a problem with just one link per cell. (2) The problem reported in bug 48803 is that links in cells with justification Centered, Right, and Distributed are completely ineffective. (3) The example in the attachment to bug 48803 is a http: URL. Terry.
Thanks Terry. I want to add two things (I thought I wrote that, but apparently I did not): - When I change the alignment, the operation is not destructive, and the original target of the link is preserved. If I change the alignment to "left", the original links return to work properly again. - If I access the cell containing the multiple links in "edit mode", the links seems to work properly even if the alignment is not left. But only in edit mode. PS: as Calc has an "edit mode" for the cells, would it be better to access a link with a simple click instead than with CTRL+Click?
Migrating Whiteboard tags to Keywords: (preBibisect) [NinjaEdit]
Only regressions should use the keyword 'preBibisect'. Removing it...
Tested in new versions:LO 5.2; LO 5.3: LO 6.0. OS:WIN7 Confirming still the same behavior like LO 3.5. - multiple links in a single cell are possible only in left cell alignment.
Also tested in OOo 3.3.0 and LO 3.3.0, considering it existed before I set up Vesion to inherited from OOo.
** 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
As requested in a recent email from QA Administrators (and in the last post here), I tested again the bug with recent versions of Libreoffice. On libreoffice 5.4.1.2: the problem is exactly the same. On Libreoffice 6.1.1: the problem is exactly the same. So the bug has not been solved yet. And that's highly expected, as it is still unassigned. I can understand it is a particular case and few users will notice it, but it is a clear bug and probably can be easily solved. Informations from "Help -> About LibreOffice": Versione: 6.1.1.2 Build ID: 5d19a1bfa650b796764388cd8b33a5af1f5baa1b Thread CPU: 4; SO: Windows 10.0; Resa interfaccia: predefinito; Versione locale: it-IT (it_IT); Calc: group threaded
Dear Calabar, 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
I can confirm that the bug has not been solved yet. Tested with the last version of Libreoffice, v6.3.1.2 (x64) on Windows 10 1903.
(In reply to Calabar from comment #10) > I can confirm that the bug has not been solved yet. > Tested with the last version of Libreoffice, v6.3.1.2 (x64) on Windows 10 > 1903. Thanks for retesting with the latest version. Setting to RESOLVED WORKSFORME as the commit fixing this issue hasn't been identified.
(In reply to Xisco Faulí from comment #11) > (In reply to Calabar from comment #10) > > I can confirm that the bug has not been solved yet. > > Tested with the last version of Libreoffice, v6.3.1.2 (x64) on Windows 10 > > 1903. > > Thanks for retesting with the latest version. > Setting to RESOLVED WORKSFORME as the commit fixing this issue hasn't been > identified. Hi, thanks for the answer. I looked at "RESOLVED WORKSFORME" definition and this case seems not to fit: the bug is clear and easily reproducible, and it seems noone fixed it somewhere. Am I missing something?
I still see the bug in a local build of commit c8e2675e, 2019-09-22, builg and running on debian-buster. I am setting but status back to NEW.
Dear Calabar, 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
As requested by an advice received by email, I confirm that the issue has not been solved still in the present versione of Libreoffice Fresh (7.3.2). I tried to save again the file with the up to date version of Libreoffice and reopened it (assuming that the issue could be due to something wrong written by the old version of Libreoffice in the sample file) but nothing changes.
Following the request of the recently received email. I confirm that the issue has not been solved still in the present versione of Libreoffice Fresh (24.2.2.2). I tried to save again the file with the up to date version of Libreoffice and reopened it (assuming that the issue could be due to something wrong written by the old version of Libreoffice in the sample file) but nothing changes. "About LibreOffice" info: Version: 24.2.2.2 (X86_64) / LibreOffice Community Build ID: d56cc158d8a96260b836f100ef4b4ef25d6f1a01 CPU threads: 8; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win Locale: it-IT (it_IT); UI: it-IT Calc: threaded