Description: Document content is invalid Steps to Reproduce: 1. new calc document 2. select some cell and press Ctrl-K 3. fill Path field with filepath like it: "e:\_works docs\2014 - Кнопки на мнемосхеме\Котлеты отдельно мухи отдельно.txt" (without quotes) 4. enter some short text to field Text 5. close settings window 6. trying go to link - it worked 7. second time press Ctrl-K link text was converted to: file:///e:/_works%20docs/2014%20-%20%D0%9A%D0%BD%D0%BE%D0%BF%D0%BA%D0%B8%20%D0%BD%D0%B0%20%D0%BC%D0%BD%D0%B5%D0%BC%D0%BE%D1%81%D1%85%D0%B5%D0%BC%D0%B5/%D0%9A%D0%BE%D1%82%D0%BB%D0%B5%D1%82%D1%8B%20%D0%BE%D1%82%D0%B4%D0%B5%D0%BB%D1%8C%D0%BD%D0%BE%20%D0%BC%D1%83%D1%85%D0%B8%20%D0%BE%D1%82%D0%B4%D0%B5%D0%BB%D1%8C%D0%BD%D0%BE.txt ok it can be normal 8. click on Path field to see it 9. click Apply, and then Ok 10. link is damaged Actual Results: Create new document Expected Results: The link should not be damaged when viewing properties Reproducible: Always User Profile Reset: No Additional Info: User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:51.0) Gecko/20100101 Firefox/51.0
No damage observed. What is this damage you speak of? Preferably, attach an example document before damage has happened. Set to NEEDINFO. Change back to UNCONFIRMED after you have provided the information. Win 7 Pro 64-bit Version: 5.4.0.0.alpha0+ Build ID: eb7b03b052ffe8c2c577b2349987653db6c53f76 CPU threads: 4; OS: Windows 6.1; UI render: default; TinderBox: Win-x86@62-merge-TDF, Branch:MASTER, Time: 2017-02-26_22:34:18 Locale: fi-FI (fi_FI); Calc: CL
Created attachment 131936 [details] normal file It is the source file
Created attachment 131937 [details] corrupted file
Here is source normal file and file with corrupted link. And this is a video how i did it https://www.dropbox.com/s/gl35cdgsum5urg1/Calc%20link.avi?dl=0 It's need to open link settings click mouse on path field, then press home key, end key or arrows. URL must be longer that field for it, if i use Cyrillic symbols each one transform to %XX and length of URL is incremented. In attached files I use only spaces as "wrong" symbols.
Created attachment 131948 [details] Video showing the creation of the document
It's just URL encoding, nothing wrong: https://en.wikipedia.org/wiki/Percent-encoding#Character_data Closing.
I understand about URL encoding. But, link after opening settings window becomes invalid value, possible it depends from url length. On my video: when I click on the link first time the document by link was opened in notepad. After open/close settings I click second time and see Message about wrong URL. If the URL is short (no encoding depends) then it not will be corrupted. Percentage encoding just did length bigger.
New steps for full enlightenment: 1. Create an empty txt file with spaces in the name, long enough that it does not fit in the Hyperlink dialog's Path input field. Example I used: Is this the real life . Is this just fantasy . Caught in a landslide . no escape from reality.txt 2. Open Calc and Ctrl-K in some cell to insert hyperlink 3. Go to Document tab, click the browse button next to Path input field, select the file you created in step 1 4. Enter some gibberish in the Text input field and click OK 5. Unfocus from the cell editing and Ctrl-click the link to check the txt file is opened 6. Ctrl-K in the hyperlinked cell to reopen the Hyperlink dialog 7. Click in the Path input field and hit End and Home on your keyboard - this is important. Notice, how when you hit End, you see the spaces and not the URL-encoded %20s. 8. Click OK and Ctrl-click the link again. My result is: The file or folder home/user/libobugs/Is this the real life . IsIs this the real life . Is this just fantasy . Caught in a landslide . no escape from reality.txt does not exist So it has appended the filename in the beginning for some reason. To confirm the theory of the URL-encoded characters, you can compare with a filename like this: Is_this_the_real_life_._Is_this_just_fantasy_._Caught_in_a_landslide_._no_escape_from_reality.txt You can also compare by dragging the Hyperlink dialog to be very wide. Arch Linux 64-bit, KDE Plasma 5 Version: 5.4.0.0.alpha0+ Build ID: 6291574d9477067e14ae493d7d9e59b19c8616ab CPU threads: 8; OS: Linux 4.10; UI render: default; VCL: kde4; Locale: fi-FI (fi_FI.UTF-8); Calc: group Built on March 23rd 2016 Arch Linux 64-bit LibreOffice 3.3.0 OOO330m19 (Build:6) tag libreoffice-3.3.0.4
** 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 Melnikov Vasiliy, 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 Melnikov Vasiliy, 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
Fixed in LO 6.4 with commit 1942182a3d1817bc539229d7fda3af69f7e295b8 Author: Caolán McNamara on Sun Jun 23 19:51:15 2019 +0100 weld HyperLink Dialog