Created attachment 181128 [details] Screencast demonstrating problem Today observed with Installation of Version: 7.3.3.2 (x64) Build ID: d1d0ea68f081ee2800a922cac8f79445e4603348 CPU threads: 12; OS: Windows 10.0 Build 19044; UI render: Skia/Raster; VCL: win Locale: de-DE (de_DE); UI: de-DE | Calc: threaded | ElementaryTheme | My normal User Profile STR: Simply click into input line after cell cursor has been placed at a cell with contents. Unfortunately that problem is difficult to reproduce, happens not very often: After I created screencast I savedmy document as sample document - and effect has vanished ... Please see screencast!
Additional Info: ---------------- a) in screencast you see input line contents vanishing when I click into it. (Cursor position looks a little strange...) b) contents reappears with <Esc> c) I did not find an obvious DUP with Query <https://bugs.documentfoundation.org/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=DUPs149870&sharer_id=19321> d) I have been observing for a long time, already with WIN7, I can't tell with which version it might have started. Also because it's so difficult to reproduce.
Maybe a dup of https://bugs.documentfoundation.org/show_bug.cgi?id=149777
Well, I can't reproduce Bug 149777 with sample there. But when Problem reappears I will have a look whether contents has not vanished, but become shifted to "second line" of input line. We will see. Thank you for the hint!
Does it happen, if the message below the input line, it's closed?
Rainer, have you witnessed the issue again since last year?
NOT reproducible with Server Installation of Version: 24.2.0.0.alpha0+ (X86_64) Build ID: 7fff4e2ca6739928f72e5f0d2eb5820823916769 CPU threads: 12; OS: Windows 10.0 Build 19045; UI render: default; VCL: win Locale: Locale: de-DE (de_DE); UI: de-DE; Theme: Colibre Calc: CL threaded – normal Test Profile created from 7.6 Also not with other View preferences (Skia, ...) I have not seen that problem for a long time, wo WFM for now.
(In reply to Rainer Bielefeld Retired from comment #6) > I have not seen that problem for a long time, wo WFM for now. Thanks for re-testing!