Description: This bug(feature) is a successor of #127881. In #127881 the problem was that the keyboard became unusable whenever the sidebar has been enabled/disabled. This is resolved now, however, the keyboard on iOS12 still behaves differently from the keyboard on iOS13 devices. On iOS13 keyboards, the user can type/modify text while having the sidebar opened. This makes it possible to quickly change the style of the text while typing. In iOS12, the user cannot modify the text while the sidebar is open. To continue editing text, the user needs to "change focus" by tapping into to text area. Steps to Reproduce: 1. Tap the sidebar icon 2. Change font style (e.g., color) 3. Type on the hardware keyboard Actual Results: 1. Tap the sidebar icon 2. Tont style changed (e.g., color) 3. Text processing/editing cannot be continued, because the keyboard is disabled and the sidebar is "in focus / active" Expected Results: 1. Tap the sidebar icon 2. Change font style (e.g., color) 3. Text processing/editing can be continued at the cursor position before the sidebar was opened and the font styles are applied immediately. Reproducible: Always User Profile Reset: No Additional Info:
Moving to NEW as agreed in the ESC meeting
This is still an issue in 4.2.5 (75) - not a major one, but it forces user to click more buttons than what is needed in a perfect world (it's also an issue in normal online). When using Apple Pages the focus will stay where the cursor is, even if I change the style (e.g. switch to bold). This way I can type, change the style and just continue typing. In the LibO iOS app the focus/cursor needs to be placed back (in most of the cases) into the document/text after changing the style before typing can be continued. It's possible not easy to solve - maybe reducing the usage of the tunneled dialogs will help in the future?
*** Bug 128919 has been marked as a duplicate of this bug. ***
Dear Andreas Gruhler, 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