Summary: | Cannot delete more than one character, or characters can get mixed up in Android Editor w AOSP keyboard | ||
---|---|---|---|
Product: | LibreOffice | Reporter: | Lionel Elie Mamane <lionel> |
Component: | Android Editor | Assignee: | Not Assigned <libreoffice-bugs> |
Status: | NEW --- | ||
Severity: | normal | CC: | aron.budea, bubu, himbeere, lo_bugs |
Priority: | medium | ||
Version: | 6.2.8.2 release | ||
Hardware: | ARM | ||
OS: | Android | ||
Whiteboard: | |||
Crash report or crash signature: | Regression By: |
Description
Lionel Elie Mamane
2020-06-14 09:01:55 UTC
Running on LineageOS 17.1-20200607-NIGHTLY-guacamole (Android version 10), API level Ilama (9) on guacamole (OnePlus 7 Pro). No Google services on phone. Are you using AOSP keyboard? (In reply to Aron Budea from comment #2) > Are you using AOSP keyboard? Yes, I am. I can confirm with AOSP keyboard, Gboard works fine. *** Bug 123437 has been marked as a duplicate of this bug. *** Let's add another case that also occurs with AOSP keyboard here: - in an empty document, switch to edit mode, - as a bit of warmup, type a bunch of characters, and erase them - type a few characters, eg. cvb => The first character will likely travel with the cursor, and the entered text becomes "vbc". If it doesn't happen, repeat the warmup steps some more. (In reply to Aron Budea from comment #6) > Let's add another case that also occurs with AOSP keyboard here: ... > => The first character will likely travel with the cursor, and the entered > text becomes "vbc". For the record, this is now solved with the following commit: https://github.com/CollaboraOnline/online/commit/2482fde532a56bd812cfa4462f7eb14e715a7e77 The originally reported bug still occurs. Dear Lionel Elie Mamane, 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 |