Bug 123437 - Nextcloud / Android Backspace Key not working
Summary: Nextcloud / Android Backspace Key not working
Status: RESOLVED DUPLICATE of bug 133977
Alias: None
Product: LibreOffice Online
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
unspecified
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-02-13 14:44 UTC by himbeere
Modified: 2020-07-30 03:39 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 himbeere 2019-02-13 14:44:14 UTC
Hello Devs.

According to the Nextcloud Devs in https://github.com/nextcloud/android/issues/3492 I should take this bug to you cool guys.

I'm currently running LOOLWSD 4.0.0 (git hash: bdf2f61) / Collabora Office 6.0-23 (git hash: 6410049). The Backspace Key does not work when trying to edit a .odt in the Nextcloud Android Client.

Any ideas?

thanks and cheers
Thomas
Comment 1 Michiel Janssens 2019-02-19 14:03:58 UTC
Same issue here, when editing via nextcloud android app (android).
Editing in Nextcloud in browser session (firefox on laptop) reponds to backspace.
LOOLWSD 4.0.0 (git hash: b956fd1)
Collabora Office 6.0-23 (git hash: 6410049)
Comment 2 Aron Budea 2019-05-01 14:35:34 UTC
Strangely I couldn't repro this with a Samsung tablet, backspace works fine there. Those who can reproduce this, it might be worth to check in Chrome as well, and confirming whether the same happens there.
Comment 3 himbeere 2019-05-01 15:16:11 UTC
Happens on all browsers on my lg g6 android pie. Foss Browser, Chrome, Firefox.
Comment 4 Aron Budea 2019-07-22 00:19:18 UTC
Ok, managed to confirm with AOSP keyboard in Collabora Online 4.0.5.
Comment 5 Aron Budea 2019-07-22 00:21:53 UTC
And it's not related to the Android app, happens from the browser as well.
As a workaround, turn off Text correction / Show correction suggestions.
Comment 6 Michiel Janssens 2019-10-01 17:31:16 UTC
Hi Aron, I tried your suggested workaround.
However with AOSP keyboard, on lineageos it does't change anything for me, even with all text correction options turned off.

I installed anysoft keyboard from f-droid, and with that keyboard active with default settings, backspace works.
Comment 7 Marcus Hoffmann 2019-11-04 12:32:00 UTC
I can confirm that disabling all text correction/suggestion options in AOSP keyboard doesn't fix the problem for me.

This is a Nexus 5X running LineageOS 15.1-20191101-microG (aka Android 8.1) Though I reproduced this as well on a OnePlus X (Android 7.1) and a Nexus 6P (Android 8.1) all running Lineage and AOSP keyboard.

Is this a bug in the keyboard or in Collbora?
Comment 8 yodatak 2019-12-08 01:44:33 UTC
Hi , this issue is not fix on Android O and Firefox , with 
LOOLWSD
4.0.9 (git hash: 97c4185)

LOKit
Collabora Office 6.0-29 (git hash: e4c7ae6)

And i can't use Libreoffice Online on Android , its realy a bad showcase for Libreoffice :/
Comment 9 Aron Budea 2019-12-09 02:45:35 UTC
(In reply to yodatak from comment #8)
> Hi , this issue is not fix on Android O and Firefox , with 
> LOOLWSD
> 4.0.9 (git hash: 97c4185)
You could give the unstable snapshots a try at:
https://www.collaboraoffice.com/code/
Mobile input should behave much better in there.

> And i can't use Libreoffice Online on Android , its realy a bad showcase for
> Libreoffice :/
Seems like a different issue, if that's the case, please open a new bug report with a detailed error description.
Comment 10 yodatak 2019-12-09 15:03:16 UTC
I use the latest form docker latest form collabora and the one in debian repository and it dont fix the issue :/ Maybe shoud i try on libreoffice:latest ?
Comment 11 Aron Budea 2020-07-30 03:39:07 UTC
It's better now, but with AOSP keyboard it still isn't working great, ie. there's bug 133977, which is about a leftover piece of this issue. Since that bug report has proper reproduction steps, I'm closing this as duplicate.

As a workaround, Gboard should work very well.

*** This bug has been marked as a duplicate of bug 133977 ***