Description: When I remove unused space after http link text it removed slow and by 2 step (part and full) Link for sample: https://awc.ashford.edu/thesis-generator Steps to Reproduce: 1. Create text document 2. Add text "https://awc.ashford.edu/thesis-generator" and add space after it will be add link on text 3. Remove space, link will be deleted slow and by two steps Actual Results: Link removed slow and by steps Expected Results: Link removed fast (and better not delete link when i remove no need space character) Reproducible: Always User Profile Reset: No Additional Info: Version: 7.0.2.2 (x64) Build ID: 8349ace3c3162073abd90d81fd06dcfb6b36b994 CPU threads: 8; OS: Windows 10.0 Build 19041; UI render: Skia/Raster; VCL: win Locale: en-US (en_US); ИП: ru-RU Calc: threaded
Additional information - Link saved, but not visible. I see hint when cursor over text and ctrl + click works
Thank you for reporting the bug. To be certain the reported issue is not related to corruption in the user profile, could you please reset your Libreoffice profile ( https://wiki.documentfoundation.org/UserProfile ) and re-test? I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' if the issue is still present
Can't reproduce in new version LibreOffice, please close bug. Also this problem in Google Docs (may be posted here by my mistake) Version: 7.1.0.0.alpha1 (x64) Build ID: 987671387712c4f9061d6216ff2f001a7bb9e57b CPU threads: 8; OS: Windows 10.0 Build 19042; UI render: Skia/Raster; VCL: win Locale: en-US (en_US); UI: ru-RU Calc: threaded
(In reply to seven from comment #3) > Can't reproduce in new version LibreOffice, please close bug. Also this > problem in Google Docs (may be posted here by my mistake) > > Version: 7.1.0.0.alpha1 (x64) > Build ID: 987671387712c4f9061d6216ff2f001a7bb9e57b > CPU threads: 8; OS: Windows 10.0 Build 19042; UI render: Skia/Raster; VCL: > win > Locale: en-US (en_US); UI: ru-RU > Calc: threaded Thanks for retesting the issue with the latest version. Setting to RESOLVED WORKSFORME since the commit fixing this issue hasn't been identified.