Description: Undo makes the initial selection large (which can be annoying with drag & drop) Steps to Reproduce: 1. open the attached file 2. Double click "lightning" 3. Drag it Between "the alley" -> Fine 4. CTRL+Z 5. Drag it again assuming the undo selection being the same as the initial selection' 6. Green highlighting is included this time Actual Results: Character before included in selection after undo Expected Results: From usability point of view not Reproducible: Always User Profile Reset: No Additional Info: Version: 7.1.0.0.alpha0+ (x64) Build ID: <buildversion> CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: Skia/Raster; VCL: win Locale: nl-NL (nl_NL); UI: en-US Calc: CL
Created attachment 164404 [details] Example file
Also in LibreOffice 3.3.0 OOO330m19 (Build:6) tag libreoffice-3.3.0.4
Telesto, it seems, that nobody could confirm this bug since more than one year. So I‘d like to ask, if it is still reproducible for you. Could you please try to reproduce it with a master build from http://dev-builds.libreoffice.org/daily/master/current.html? I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' if the bug is still present in the latest version.
Dear Telesto, 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
Still behaving the same Version: 7.3.0.0.alpha0+ (x64) / LibreOffice Community Build ID: d5e55d204b71710eb5eb5d2c683dd6698626df3c CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: Skia/Raster; VCL: win Locale: en-US (nl_NL); UI: en-US Calc: CL
I confirm it with Version: 7.2.1.2 (x64) / LibreOffice Community Build ID: 87b77fad49947c1441b67c559c339af8f3517e22 CPU threads: 4; OS: Windows 10.0 Build 19043; UI render: Skia/Raster; VCL: win Locale: de-DE (de_DE); UI: de-DE Calc: CL Please see your own bug 141738 (SELECTION: It's not visible, that blank space before the word is also selected, if you double-click a word) So I support consistency here, but please decide, what you want a) double click should also select blank space before b) blank space before shouldn't be inculded after undo => NEEDINFO
(In reply to Dieter from comment #6) > I confirm it with > > Version: 7.2.1.2 (x64) / LibreOffice Community > Build ID: 87b77fad49947c1441b67c559c339af8f3517e22 > CPU threads: 4; OS: Windows 10.0 Build 19043; UI render: Skia/Raster; VCL: > win > Locale: de-DE (de_DE); UI: de-DE > Calc: CL > > Please see your own bug 141738 (SELECTION: It's not visible, that blank > space before the word is also selected, if you double-click a word) > > So I support consistency here, but please decide, what you want > > a) double click should also select blank space before > b) blank space before shouldn't be inculded after undo > > => NEEDINFO Based on the logic, I would opt for B. A blank space isn't always added. I even could argue the insertion of empty space before being wrong in general. A space being inserted out of nowhere . But Heiko sees empty space insertion as feature, not a bug IIRC. In that case this being side-effect (bug), caused by the feature.
I had a closer look inside. Since you have a blank space before and after lighting, you can easily see, that one space is dragged together with the word "lighting", because otherwise there would be two spaces at the end. And undo makes this visible. So the bug you describe is just a variant of bug 141738 *** This bug has been marked as a duplicate of bug 141738 ***