Description: When entering edit mode in a spreadsheet on iOS the focus is not set in a way that a user can immediately start to type something. Right now a user needs to first manually click on a cell or into the input bar in order to be able to actually type something. I think it would be good to explicitly set the focus in a way that a user is able to enter text or move the cell selection with the arrow keys. Steps to Reproduce: 1. Open a spreadsheet document on iOS 2. Enter edit mode 3. Immediately start to type something Actual Results: Nothing really happens, the input doesn't show up. Expected Results: A user would expect that text which was entered shows up or the cell selection can be moved with the arrow keys. Reproducible: Always User Profile Reset: No Additional Info: This is probably a low prio bug but IMHO it's something many user will run into when using spreadsheets on iOS. If a simple fix can help to improve this we can make the user experience a bit better I think.
Moving to NEW as agreed in the ESC meeting
Looking at this now.
Fixing this is made more complicated by the fact that without a hardware keyboard, what we might end up after a fix is a situation where the on-screen keyboard is displayed right away after the make-editable button is pressed. That is probably not ideal either.
Hmm, as you say "This is probably a low prio bug" I will leave this for a while and go on to some easier one.
Out of curiosity I checked this with 4.2.8 (62). It's a tad better as I can use the coursor keys of the (semi attached) hardware keyboard right after switching into edit mode and after using the cursor keys I can also start typing letters/numbers. Typing right away (w/o using the cursor keys) is however still not possible, so I keep the state of this issue as is.
Dear Nicolas Christener, 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