vogon

the evil "Website Boy"

member of @staff, lapsed linguist and drummer, electronics hobbyist

zip's bf

no supervisor but ludd means the threads any good


twitter (inactive)
twitter.com/vogon
bluesky
if bluesky has a million haters I am one of them, if bluesky has one hater that's me, if bluesky has no haters then I am no more on the earth (more details: https://cohost.org/vogon/post/1845751-bonus-pure-speculati)
irl
seattle, WA

apparently the brokenness of the tags and content warning fields in the post composer are related to widely-known issues with input events on android software keyboards being a complete nightmare that doesn't match any other platform on earth. this thread tipped me off that most of the problem is fixed in android 12L aka android 12v2 aka "API level 32", which I was able to verify with a device emulator; the fields work as expected with gboard in firefox.

unfortunately, I have no idea if or when you will ever get android 12L on your device.

edit: as @shork pointed out down in the comments, it appears to also be broken on deployed android 12L devices with newer, production builds, so maybe the behavior was changed accidentally during development and they changed it back before ship? I love computing.


You must log in to comment.

in reply to @vogon's post:

well, shoot. both of those build strings are unambiguously newer than the ones I tested with, so maybe the keyboard handling in the build that comes with android studio is uniquely not-broken. thanks for the additional details!

we'll definitely reach out if we think there's something that we need help testing -- but thankfully, the bug reproduces just fine in the emulator! thanks for offering, though, and thank you for tipping us off that the bug was (unfortunately) not going to magically solve itself!

"Let’s say you have a node that is an atom and there is nothing selectable inside of that node. What Android often does is that when you backspace onto that node, Android will just give up and dismiss the keyboard" incredible