Bug 123492 - Cannot select text using keyboard in read-only mode
Summary: Cannot select text using keyboard in read-only mode
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
6.2.0.3 release
Hardware: x86-64 (AMD64) All
: medium minor
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: Selection
  Show dependency treegraph
 
Reported: 2019-02-16 03:48 UTC by thangalin
Modified: 2025-05-25 03:11 UTC (History)
4 users (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description thangalin 2019-02-16 03:48:12 UTC
Description:
After opening a spreadsheet downloaded from the Internet (in read-only) mode, the user cannot select any text using keyboard navigation.

Steps to Reproduce:
1. Download a spreadsheet (e.g., https://www.ncbi.nlm.nih.gov/pmc/articles/PMC5382278/bin/ncomms14845-s2.xlsx)
2. Open in read-only mode.
3. Press F2 to edit a cell.
4. Use the arrow keys to navigate within the cell.
5. Use shift + arrow keys to select text within the cell.

Actual Results:
Arrow keys to not move the cursor position within the text, despite a cursor being visible and flashing.

Expected Results:
User can navigate the cell text using arrow keys.

User can highlight text using arrow keys and shift key modifier.


Reproducible: Always


User Profile Reset: Yes



Additional Info:
Read-only does not mean "cannot copy". A read-only document should still have all the regular functionality for copying text when reviewing a cell's contents.

A work around is to use the mouse to select text.
Comment 1 raal 2019-02-16 05:52:55 UTC
Confirm with Version: 4.1.0.0.alpha1+
Build ID: 863d38fbfa4fb4861e476828c46410602100919 and LO 6.3 master
Comment 2 figioteo 2019-02-21 10:29:47 UTC
Confirmed with 6.2.0 version on MacOS.
Comment 3 thangalin 2019-03-02 07:45:29 UTC
Version: 6.2.0.3
Build ID: 6.2.0-3
CPU threads: 16; OS: Linux 4.20; UI render: default; VCL: gtk3; 
Locale: en-CA (en_CA.UTF-8); UI-Language: en-US
Calc: threaded
Comment 4 QA Administrators 2021-03-14 04:18:27 UTC Comment hidden (obsolete)
Comment 5 thangalin 2021-03-14 18:21:49 UTC
Bug still exists.

Version: 7.1.0.3 / LibreOffice Community
Build ID: 10(Build:3)
CPU threads: 16; OS: Linux 5.9; UI render: default; VCL: gtk3
Locale: en-CA (en_CA.UTF-8); UI: en-US
7.1.0-2
Calc: threaded
Comment 6 Diana Vides 2023-05-25 05:56:15 UTC
The bug still present in version 7.5.3.2 and 7.6.0.0.alpha1+

Version: 7.5.3.2 (X86_64) / LibreOffice Community
Build ID: 9f56dff12ba03b9acd7730a5a481eea045e468f3
CPU threads: 6; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win
Locale: es-ES (en_US); UI: en-US
Calc: threaded


Version: 7.6.0.0.alpha1+ (X86_64) / LibreOffice Community
Build ID: f4c24da1e7f11664e0d2f688d2531f068e4a3bc0
CPU threads: 6; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win
Locale: en-US (en_US); UI: en-US
Calc: CL threaded
Comment 7 QA Administrators 2025-05-25 03:11:28 UTC
Dear thangalin,

To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present.

If you have time, please do the following:

Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the information from Help - About LibreOffice.
 
If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice.

Please DO NOT

Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not 
appropriate in this case)


If you want to do more to help you can test to see if your issue is a REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/

2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword


Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team

MassPing-UntouchedBug