Steps how to reproduce with Parallel Dev-Installation of "LibreOffice 3.5.0 Beta1 - WIN7 Home Premium (64bit) German UI [Build-ID: 7362ca8-b5a8e65-af86909-d471f98-61464c4] Windows_Release_Configuration 11-Dec-2011 06:51" 1. Open attached "sample1.odt" 2. Try to click text "Try to click here" in frame Expected: Caret appears at mouse click location Actual: Caret remains somewhere in document Trying the same with 3.4.5RC1 everything works as expected, so Regression
Created attachment 54503 [details] Sample Document Details see in original report!
Not a new Beta1 problem, also visible with Server installation of Master "LibO-dev 3.5.0 – WIN7 Home Premium (64bit) English UI [(Build ID: 5d1a991-4cb1bac-ca7e6f5-9125509-ce71330)]" (111109) already broken in Server installation of Master "LibO-dev 3.4.5 – WIN7 Home Premium (64bit) English UI [(Build ID:d337f79-a24c961-2865670-9752b71-7f8fd43 2fdd60d-fd28b6a-fd7bf20-aa369cb-28da3fb 6a9633a-931d089-ecd263f-c9b55e9-b31b807 82ff335-599f7e9-bc6a545-1926fdf)]"
Reproducible with LibO 3.5.0 Beta1 LOdev 3.5.0 · Build ID: 7362ca8-b5a8e65-af86909-d471f98-61464c4 [LibO-Dev_3.5.0beta1_Win_x86_install_multi.msi · 13-Dec-2011 · http://dev-builds.libreoffice.org/pre-releases/win/x86/ ]. I had to - select the frame, and then - press 'Enter' ... Test case *not* reproducible with a newly created text document in LibO 3.5.0 Beta1, opened with LibO 3.5.0 Beta1. → 'Test frame 350b1.odt' Test case *not* reproducible with a newly created text document in LibO 3.4.4 release, opened with LibO 3.5.0 Beta1. → 'fdo#43892_frame.odt' For the record: Opening 'sample1.odt' works fine with LOdev 3.5.0 Build ID: 91e222d-6e20485-4c1bcb5 [libreoffice-3-5~2011-12-14_20.39.46_LibO-Dev_3.5.0beta1_Win_x86_install_en-US.msi · 15-Dec-2011 · Index of /daily/Win-x86@6-fast/libreoffice-3-5 ]
Created attachment 54526 [details] Test frame 350b1.odt
Created attachment 54527 [details] fdo#43892_frame.odt
Sorry, reproducible in LibO 3.5.0 Beta1 with *all* attached text documents, and formatted as 'Wrapped Through'.
Also reproducible (all attached *.odt, formatted as 'Wrap Through') [on WinXP 32b] with LibO Master LOdev 3.5.0 Build ID: 485138f-e92bf75-4c1bcb5 [master~2011-12-06_21.37.02_LibO_3.5.0beta0_Win_x86_install_en-US.msi · 07-Dec-2011 · Index of /daily/Win-x86@6-fast/master] Not reproducible, and works fine for me (all attached *.odt, formatted as 'Wrap Through') with LibO 3.5.x LOdev 3.5.0 Build ID: 91e222d-6e20485-4c1bcb5 [libreoffice-3-5~2011-12-14_20.39.46_LibO-Dev_3.5.0beta1_Win_x86_install_en-US.msi · 15-Dec-2011 · Index of /daily/Win-x86@6-fast/libreoffice-3-5]
Works for me with LibO 3.5.0 Beta2 [LOdev 3.5.0beta2 · Build ID: 8589e48-760cc4d-f39cf3d-1b2857e-60db978] (on WinXP 32b · UI: en-US · all attached *.odt, formatted as 'Wrap Through')
WFM with "LibreOffice 3.5.0 RC3 German UI/Locale [Build-ID: 7e68ba2-a744ebf-1f241b7-c506db1-7d53735] on German WIN7 Home Premium (64bit)
Same here with 64bit 3.5.0 final on Kubuntu. p.
*** Bug 47200 has been marked as a duplicate of this bug. ***
Created attachment 63313 [details] Another Problem File Cannot edit some of the frames in this file.
This is still broken for me in: LibreOffice 3.5.4.2 Build ID: 165a79a-7059095-e13bb37-fef39a4-9503d18 I attached the problem file (Another Problem File). It originated as a Word document several years ago, and has been edited as an oo.org document through several versions. The only way that I can find to edit the problem frames is to select the frame and then press "Enter".
The original problem still is WFMwith 3.5.5.1, LibreRay's problem is reproducible with 3.5.5.1., so it's something different with similar symptoms. I close this one again submit a new Bug for for the new problem. @LibreRay: <https://wiki.documentfoundation.org/BugReport_Details#How_to_reopen_Bugs>
I'm very sorry if I breached protocol. I read this: - If the old bug is on Status WORKSFORME feel free to reopen after you checked carefully that you really observe the reported bug and whether your LibreOffice Version can contain the FIX therefore check the Whiteboard target information!). I only reopened it because I thought this applied (i.e. there was no indicated fix, just a closed with "WORKSFORME").
Comment on attachment 63313 [details] Another Problem File Submitted new Bug 51306 for problem with this document
<http://wiki.documentfoundation.org/BugReport_Details#Version>