Description: 1. Ensure AutoCorrect is off: Tools > AutoCorrect > While Typing = False. 2. Type: ``` * http://google.com[Google] ``` This is AsciiDoc format for hyperlinks, but you could type something different, e.g. ``` foo bar[baz] ``` 3. Select the hyperlink (example 1) or "bar" (example 2) and cut it. 4. Notice that there is no space now: ``` *[Google] foo[baz] ``` Expected: ``` * [Google] foo [baz] ``` Tested with 6.2.7.1 (x86) and 6.4.0.0.alpha0+ (x86). Steps to Reproduce: - Actual Results: - Expected Results: - Reproducible: Always User Profile Reset: Yes Additional Info:
Created attachment 155217 [details] spaces present on pasted strings Can not confirm on Windows 10 Ent 64-bit en-US with Version: 6.3.2.2 (x64) Build ID: 98b30e735bda24bc04ab42594c85f7fd8be07b9c CPU threads: 8; OS: Windows 10.0; UI render: GL; VCL: win; Locale: en-US (en_US); UI-Language: en-US Calc: threaded nor with current master/6.4.0alpha1+ Version: 6.4.0.0.alpha1+ (x64) Build ID: 3e8fb860d92160e41a1aef5a0a53e4447120eb2e CPU threads: 8; OS: Windows 10.0 Build 18362; UI render: GL; VCL: win; Locale: en-US (en_US); UI-Language: en-US Calc: threaded The pasted string keep their spaces as noted by the NPC blue dots.
Looking on your screenshots I'm not sure you understand the description correctly. Well, it's my fault, let me explain better. Here is the example: * https://google.com/[Google] It have an asterisk, a hyperlink, and a hyperlink description. I.e.: * hyperlink: https://google.com/ * hyperlink description: [Google] Select the hyperlink part and cut it with Ctrl-X. Before: * https://google.com/[Google] After: *[Google] Expected: * [Google]
(In reply to John from comment #2) Sorry, on a different system (with 6.3.2.2 installed) still can not reproduce. With mouse select, then a <Ctrl>+X, or simply a <Del> key delete--the space remains. Maybe you could work up a test file and steps to reproduce.
Dear John, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping
Dear John, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-FollowUp