OS: Debian Jessie amd64 LibreOffice version: 5.0.2 (english) installed from jessie-backports Steps to reproduce: (for shorter writing, I use abbreviations: $RIGHTURL="https://www.freevoipdeal.com/calling_rates/#/#letter-N" $WRONGURL="https://www.freevoipdeal.com/calling_rates/#/%23letter-N" ) Calc: 1. open Calc 2. enter in A1: =HYPERLINK("$RIGHTURL";"$RIGHTURL") 3. go back to A1 and see it indeed has the correct formula, and that the output of the cell is $RIGHTURL 4. additionally, hover with mouse over hyperlink, the tooltip says $RIGHTURL. 5. ctrl+click the hyperlink 6. Firefox (well, Iceweasel in my case) opens, the address bar says $WRONGURL 7. see that Firefox doesn't scroll to the "letter-N" section of the page Impress: 1. open Impress 2. select: Insert -> Hyperlink, type in Target field: $RIGHTURL, choose OK 3. see the hyperlink title is $WRONGURL 4-7. same as Calc 4-7. Writer: 1. open Writer 2-3. same as Impress step 2-3. 4. additionally, hover with mouse over hyperlink, the tooltip says $WRONGURL. 5. right-click on the hyperlink, choose "Edit Hyperlink" 6. see both Title and Text fields say $WRONGURL 7-9. same as Calc/Impress 5-7. Note the differences in step 4 (tooltip), only Writer says $WRONGURL. Also, in Writer/Impress at step 2, when I aditionally put $RIGHTURL in the Text field (instead of leaving blank), the hyperlink title is $RIGHTURL. When instead as URL I try http://localhost/### , FF goes to http://localhost/#%23%23 So it seems only the first # survives unscathed (I guess because there's already some code to protect such HTML-section-URLs). Starting Firefox with these URLs as command line argument works fine (scrolls to section). I never needed this functionality, so I don't know in which version this bug appeared. Regardless, thanks! Gert
Repro. Win 7 Pro 64-bit Version: 5.1.0.0.alpha1+ Build ID: b216cc1b8096eb60c27f67e8c27b7cd756c75e38 TinderBox: Win-x86@62-merge-TDF, Branch:MASTER, Time: 2015-11-12_00:06:20 Locale: fi-FI (fi_FI) 3.5.0
** 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 on a currently supported version of LibreOffice (5.1.6 or 5.2.3 https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System 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) 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: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug-20170103
bug still present in 5.2.3.3 OS: Debian Jessie 8.6 amd64 Libreoffice version: 1:5.2.3-2~bpo8+1 (dutch) installed from jessie-backports Version: 5.2.3.3 Build ID: 1:5.2.3-2~bpo8+1 CPU Threads: 2; OS Version: Linux 4.7; UI Render: default; VCL: gtk3; Locale: nl-NL (nl_NL.UTF-8); Calc: group
** 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
I am unsure this is a bug. Why would that be a valid URL? Hashes (or "Number signs" #) have special meaning in URLs - they are reserved; namely, they mark a fragment part of the URL - and there may be only one such unencoded mark; all other hashes must be url-encoded (see RFC 3986 [1] sections 1.2.3, 2.2, etc.). So the "$RIGHTURL" from comment 0 is actually "$INVALIDURL"; and my proposal would be close it NOTABUG. [1] https://tools.ietf.org/html/rfc3986
Yes, the first "#" sets off the fragment part. And any further "#" are apparently escaped by LO when it passes on the URL (which is legal for LO to do, even though it may not be helpful for certain consumers that would interpret the non-escaped URL in a nonstandard way).