When I selected some cells in one of sheets and then switch or create another sheet, the selected area disappear.
Steps to reproduce:
1. Selected the cells from A1 to B2;
2. Click the "+" button to create another sheet;
3. Switch to the first sheet which the selected cells in.
The selected area from (A1:B2) to A1.
The selected area is (A1:B2)
Operating System: Windows 7
Version: 126.96.36.199 release
Win 7 64-bit Version: 188.8.131.52.alpha1+
Build ID: 8b21b5cbe78945b27525b4ce78ae3d981f90590f
TinderBox: Win-x86@39, Branch:master, Time: 2014-11-06_03:55:51
This behavior (losing cell selection) also occurs when switching to print preview and back to the current sheet.
Inherited from OOo, see https://bz.apache.org/ooo/show_bug.cgi?id=93938
Set "Hardware" to "All".
By the way, a selected/marked range also disappears in Writer when going to Print Preview and back! Should this behavior in Writer be another bug or can we set "Component" from "Calc" to "LibreOffice" or "UI"? I think all components of LibreOffice use a common code that causes this bug.
Confirmed in Version: 184.108.40.206
Build ID: 7074905676c47b82bbcfbea1aeefc84afe1c50e1
CPU Threads: 8; OS Version: Windows 6.2; UI Render: default; Layout Engine: new; Calc: CL
(In reply to Thomas Lendo from comment #3)
> By the way, a selected/marked range also disappears in Writer when going to
> Print Preview and back! Should this behavior in Writer be another bug or can
> we set "Component" from "Calc" to "LibreOffice" or "UI"? I think all
> components of LibreOffice use a common code that causes this bug.
I asked a Calc dev and you should create a new report for the Writer issue.
For Writer: Bug 106038 - Selected range of text disappears when going to Print Preview and back
*** Bug 101056 has been marked as a duplicate of this bug. ***
Version: 220.127.116.11.alpha0+ (x64)
Build ID: 18c5089df091bddeb8c2dc339776671964389040
CPU threads: 8; OS: Windows 10.0; UI render: GL;
TinderBox: Win-x86_64@42, Branch:master, Time: 2018-09-12_23:24:12
Locale: de-AT (de_AT); Calc: CL
*** Bug 128520 has been marked as a duplicate of this bug. ***