I recall reporting this same problem several versions ago and it was fixed relatively quickly, but now I can't locate that bug report. When opening and displaying Writer's Find dialog using Ctrl+F, the usual practice in most versions was to place the cursor in the dialog's field, but the behavior in 5.0* now is to leave the cursor active in the main document. The ironic thing is that I was preparing a document to describe and show how to replicate a related group of bugs, and just downloaded the new 5.0 earlier today in order to make sure none of them were fixed in the meantime. Please fix this. I'm old and get confused when I realize the cursor is not in the find dialog, so I put it there and retype what I'm looking for. Strangely enough, it finds what I had just typed in the document by mistake. * Specifically Version: 5.0.0.1; Build ID: 9a0b23dd0ab9652e0965484934309f2d49a7758e; Locale: en-US (en_US.UTF-8) Just for the record, I'm using 64 bit Ubuntu 14.04 LTS.
maybe Linux specific issue since I don't reproduce it under Win8.1x64 using a recent LibO 5.1.0.0 alpha daily build
I now believe that this behavior only occurs the first time I open the Find dialog in a given session; if I close the dialog and subsequently reopen it without closing Writer, the cursor is placed in the text entry box as soon as I press Ctrl+F. And re: Tommy27's comment, I haven't yet loaded v5.0 into any other environment, so he may be correct. If I decide to do that (still fixing all the formatting changes that occurred when I loaded the doc I was last working on in 4.4 into 5.0), I'll post the results.
Opened Writer so that the Find bar is not visible. Could not reproduce. RC2 should arrive any day now, so I recommend to retest with it: https://wiki.documentfoundation.org/ReleasePlan/5.0 Ubuntu 15.04 64-bit Version: 5.1.0.0.alpha1+ Build ID: 3ecef8cedb215e49237a11607197edc91639bfcd TinderBox: Linux-rpm_deb-x86_64@46-TDF-dbg, Branch:master, Time: 2015-06-20_00:06:19 Locale: en-US (en_US.UTF-8)
For me not reproducible with LO 5.1.0.1, Win 8.1
@Frank please retest with latest LibO 5.0.4.2 and tell if issue persists. status -> NEEDINFO
Using version: 5.0.3.2, the problem no longer exists. That was the last version I downloaded and I have no plans to continue updating. As far as I'm concerned, the bug can be closed. Frank
Thanks, Frank. Setting to WFM.