When I change to another programm (i.e. to a pdf-reader) while a filled cell in calc is marked and I change back to calc, the cursor goes into the marked cell and the old value of the cell is not visible anymore. Changing the cell via Return or a arrow leaves the cell empty. Behaviour should be that the cell still is marked but without the cursor in the cell.
Changing with ALT+TAB
I cannot confirm with Version: 6.3.0.0.alpha0+ Build ID: 630db80d17616d635cf2e5f1d5a0852428b794a3 CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: x11; Locale: cs-CZ (cs_CZ.UTF-8); UI-Language: en-US write text into cell ALT+TAB to another program ALT+TAB back return text is here.
Created attachment 151544 [details] Screencast I added a screencast that shows the problem.
You can see at 00:02 that cell is empty before Alt+Tab. Please paste here informations from Help->About
Version: 6.2.3.2 Build-ID: 1:6.2.3-0ubuntu0.18.04.1~lo1 CPU-Threads: 4; BS: Linux 4.15; UI-Render: Standard; VCL: kde5; Gebietsschema: de-DE (de_DE.UTF-8); UI-Sprache: de-DE Calc: threaded
Created attachment 151551 [details] 2nd screencast Made a secend screencast in which I did not change by ALT+TAB but by taskbar. Here it happens at the second change. I did not recognize before that it doesn't appear everytime (rechecked with ALT+TAB and there it also doesn't happen everytime).
Created attachment 151620 [details] 3rd screencast New information: It happens for sure, when in the other program, the cursor is focused in any kind of textfield i.e. the address bar of the browser. It doesn't happen when I change i.e. between calc and gimp (gimp without any file opened) I made a third screencast to visualize it.
I cannot reproduce (with Firefox address bar). What if you try running from the command line with SAL_USE_VCLPLUGIN=gen libreoffice Arch Linux 64-bit Version: 6.4.0.0.alpha0+ Build ID: b9a776837462eeb6d50d0decc42604c0c3008eb1 CPU threads: 8; OS: Linux 5.2; UI render: default; VCL: kf5; Locale: fi-FI (fi_FI.UTF-8); UI-Language: en-US Calc: threaded Built on 11 August 2019
Updated to 6.3.0.4 and the problem is gone. In the meantime it helped me not to work under KDE-Plasma but in gnome where the problem didn't occur. Maybe it was a preference in the Plasma desktop.