Created attachment 149759 [details] a sample writer file demonstration the problem When a piece of text which starts with a forward slash is selected and then a hyperlink defined in the insert hyperlink dialog, the result will be two links with similar targets but with differing texts. The text for the first link is a single slash and for the next link is the remainder of the text. Steps to reproduce: sample text = "/for" {without double quotes of course} sample link = "http://www.example.com" 1 - create the link with the sample text and link and save the file 2 - rename the file to a zip file 3 - extract the zip file 4 - open the "content.xml" file in the extracted folder 5 - search for the sample link 6 - you will find two links one with a "/" and another with the "for": first link <text:a xlink:type="simple" xlink:href="http://www.example.com/" text:style-name="Internet_20_link" text:visited-style-name="Visited_20_Internet_20_Link">/</text:a> second link <text:a xlink:type="simple" xlink:href="http://www.example.com/" text:style-name="Internet_20_link" text:visited-style-name="Visited_20_Internet_20_Link"><text:span text:style-name="T1">for</text:span></text:a></text:p></office:text></office:body></office:document-content>
This problem is only seen when inserting a hyperlink to a selected text using context (or top bar) menu. If no text selected and the link text entered in the hyperlink dialog, this behavior is not observed.
great article, I was very impressed about it, wish you would have stayed next share http://mutilateadoll2game.com
Weird: I got inconsistent results. First try, with Ctrl-K, no repro. Second try, with menu item, repro. Third try, with Ctr-K, repro. Will check with older versions next. Arch Linux 64-bit Version: 6.3.0.0.alpha0+ Build ID: e967aea2d8cc4f9fc608cb726cb474c184fb61de CPU threads: 8; OS: Linux 5.0; UI render: default; VCL: gtk3; Locale: fi-FI (fi_FI.UTF-8); UI-Language: en-US Calc: threaded Built on 7 April 2019
Also confirmed on Windows 10. Bibisected on Linux with 43all to range https://gerrit.libreoffice.org/plugins/gitiles/core/+log/43c7830b03d141ae11d8617c0fdabefa32dd243c..ce97851773a06103504972eb2771eecd7dd81e36 Unfortunately, the range is huge and by quickly checking I did not find anything relevant. The inconsistent results mentioned in my previous comment also cast suspicion on any bibisect.
Let's use keyword notBibisectable, then. Btw, two other bug reports related to hyperlink editing have been bibisected to this range (bug 99912 and bug 124296), which makes me think the same change or series of changes might be responsible for these.
Dear msaghaei, 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