steps: 1. open writer 2. paste 'https://fontlibrary.org/en/search?lang=arabic&order=' (without quotes) 3. press spacebar so it can be automatically converted into hyperlink 4. last '=' isnt included as part of hyperlink Version: 6.0.0.0.alpha1+ Build ID: 43d6b11a5c1dda0cc2c1e06c768eece25051a56c CPU threads: 2; OS: Linux 4.4; UI render: default; VCL: gtk2; Locale: en-US (en_US.UTF-8); Calc: group
Confirmed in Version: 6.0.0.0.alpha1+ Build ID: d30522e46ca884e9bc74af21711d9537e8118859 CPU threads: 4; OS: Linux 4.10; UI render: default; VCL: gtk3; Locale: ca-ES (ca_ES.UTF-8); Calc: group
Same happens with '#'
bug 45777 seems similar. I'll take a look
Detecting a URL in free-form text uses some heuristics to determine what part of the text constitutes a URL and, especially, where exactly the found URL ends and what characters (that might even legally be part of the URL) following it are instead "punctuation" in the free-form text. The heuristics currently employed by LO (as implemented in URIHelper::FindFirstURLInText, svl/source/misc/urihelper.cxx) consider a trailing '=' at the end of the fragment, query, or path part (if it does not detect any further parts following that part) as delimiting "punctuation" rather than as part of the URL. Interestingly, LO appears to not be only with using such a heuristic. Witness whatever software is responsible for it having converted the free-form text in comment 0 into > 2. paste '<a href="https://fontlibrary.org/en/search?lang=arabic&order">https://fontlibrary.org/en/search?lang=arabic&order</a>=' (without quotes) i.e., having decided that the trailing '=' should not be treated as part of the URL, either. Is anybody aware of a pressing need to change the heuristic to treat a trailing '=' in an otherwise non-empty query part not followed by a fragment part (as exemplified in the original request in comment 0) as being part of the URL? (And also treat such a '=' as part of the URL in even more places? Also at the end of an otherwise empty query part? Also at the end of an empty/non-empty path or fragment part?) Otherwise, I would suggest to not touch the current heuristics. Such heuristics are always somewhat brittle, and changing them has always potential for (real or perceived) regressions (e.g., somebody else might be upset by finding a trailing '=' now be considered part of the URL, after decades of different behavior). And regarding "Same happens with '#'" (comment 2): A '#' starting a fragment part that would be empty is indeed not considered by the heuristics as being part of the URL. I consider that a feature rather than a bug.
To me this is a bug as equal is a valid character of the query part of the url, so i tested the issue on other word processors Work like LO * Word 2013 * Softmaker TextMaker Work different to LO * WPS Writer * Google Docs * WordPerfect
> Work like LO > * Word 2013 > * Softmaker TextMaker Same in Word 2010. However, Word 2010 includes the # in 1. http://crashreport.libreoffice.org/stats/# 2. http://crashreport.libreoffice.org#
I abandoned my patch in https://gerrit.libreoffice.org/#/c/44241/
** 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 Yousuf Philips (jay) (retired), 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 Yousuf Philips (jay) (retired), 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
Still present. Version: 25.8.3.2 (X86_64) Build ID: 8ca8d55c161d602844f5428fa4b58097424e324e CPU threads: 4; OS: Linux 6.11; UI render: default; VCL: kf5 (cairo+xcb) Locale: en-US (en_US.UTF-8); UI: en-US Calc: threaded == Additional tests == Works like LO * Word 2016, Word 2019 Works different to LO * OnlyOffice * Word for Web (onedrive)