掲示板 Forums - Unable to delete quote blocks

After a little more experimentation, I've found that you can change the formatting of the current paragraph using the button with the paragraph formatting mark and selecting "text."

Given that the browser version allows deleting quote blocks with backspace, I'm still not sure the behavior on Android is intentional, but at least there's some way to get out of the quote block.

While trying to show the issue in a screen capture, I figured out that it has to do with the keyboard being used. Here's a video showing the behavior I'm talking about:

odysee.com/@temporarychannelname:2/Renshuu-Android-keyboard-issue:0?view=shorts

I'm using /e/OS and the default keyboard is the AOSP keyboard. I also have a fairly obscure polytonic Greek keyboard installed, as well as Sumire Japanese keyboard.

With the AOSP keyboard, I frequently can't enter a new line with the enter key, but with the Sumire keyboard everything works fine (I actually had to switch to it to enter the new line for this paragraph). The same happens with the Greek keyboard - enter occasionally just stops working.

The frustrating thing for trying to track down the bug is that the behavior is inconsistent; the new line for this paragraph was entered with the AOSP keyboard with no problem. As far as I can tell, the best way to reproduce the newline issue is to create a new line, then delete it. After that, the enter key on the non-Japanese keyboards stops working.

For quotes, similarly, everything works as expected with the Sumire keyboard. With the other keyboards, once you delete all of the text inside the quote, the quote box can't be deleted, and tapping anywhere outside of the empty quote box loses focus on the post editor and causes the keyboard to disappear. Canceling the post and then reopening it results in the same behavior. Canceling the post and then tapping "quote" again results in a new quote being put above the empty quote box, and in that state, I can delete the empty quote box.

Hopefully this is enough to go on. If there are any other combinations or variables you'd like me to test, just let me know.

It looks like it would require a rooted phone for you to install the AOSP keyboard (according to xdaforums.com/t/guide-install-lineageos-aosp-keyboard-on-any-phone.3828625/) so that's probably a no-go, but you can install "Fossify Keyboard Beta," which I've confirmed has the same problem, as a normal app. I also checked gboard and confirmed it can clear out the quote blocks normally.

Results for gboard:

Backspace key:

{
"key": "Backspace",
"keyCode": 8,
"which": 8,
"code": "",
"location": 0,
"altKey": false,
"ctrlKey": false,
"metaKey": false,
"shiftKey": false,
"repeat": false
}

Enter:

{
"key": "Enter",
"keyCode": 13,
"which": 13,
"code": "",
"location": 0,
"altKey": false,
"ctrlKey": false,
"metaKey": false,
"shiftKey": false,
"repeat": false
}

Results for AOSP:

Backspace: no event registered (nothing happens)

Enter:

{
"key": "Enter",
"keyCode": 13,
"which": 13,
"code": "",
"location": 0,
"altKey": false,
"ctrlKey": false,
"metaKey": false,
"shiftKey": false,
"repeat": false
}

Results for Sumire:

same as for gboard

Results for Hoplite:

Neither backspace nor enter register an event. Pressing other keys registers key code 229, "process".

Results for Fossify:

same as for AOSP

Here's one more tool. Unfortunately, the textfield is also the output field, but without copying the text over, try this:

1. Press backspace when the field is empty

2. Press a different key (and get some output)

3. Press backspace again.

For the ones with no response, I'm wondering if #1 and #3 will be different.

unixpapa.com/js/testkey.html

My guess as to the different behavior is that the AOSP keyboard uses backspace to undo autocorrect insertions. If it thinks a word is misspelled and punctuation, a space, a newline, or an emoji is entered, the misspelled word is replaced with the suggestion and the whitespace/punctuation/emoji is entered. If backspace is then pressed, there are three possible actions:

1. If the previous character is a space, the space is deleted and the insertion is reverted
2. If the previous character is punctuation, the insertion is reverted, but the punctuation is not deleted unless you press backspace again
3. If the previous character is an emoji or newline, the previous character is deleted and the insertion is not reverted

Unfortunately, turning off autocorrect doesn't change the behavior, it still uses keycode 229. For gboard, it still uses autocorrect, but pressing backspace doesn't undo the insertion.

On a related note, it looks like the way to get the Sumire keyboard to use code 229 is just to press backspace while a character is being edited (I assume because deleting the character might involve deleting one or more dead key inputs too). So さ -> enter -> backspace uses code 8, but さ -> backspace uses 229.

One thing I've found works well on another forum, which uses Xenforo, is that it allows you to edit posts in plaintext mode, so everything appears wrapped in tags instead of formatted. If the Renshuu text editor uses tag-based formatting under the hood, is that something that could be exposed to the user with a reasonable amount of effort?