Sync post creation interface prevents me from using my third party smartphone keyboard in the title box.

Hi! I love sync, and I've just encountered the first thing that lowered my experience.

When creating a post, such as this one, I have a problem with the title box : I can't use my third party keyboard that's installed on my smartphone.

I use SwiftKey, a keyboard that allows me to slide from one keyboard letter to the other in order to write faster. I have big thumbs, and touching each letter individually is a problem for me, so you could say I use this keyboard as an accessibility tool.

So, on the post creation interface, in the title box (and only in the title box), I can't swipe on my keyboard. This box will only accept one letter at the time, and it's really burdensome for me.

Writing the title of this post took me around 3 minutes. Sometimes I'll write it somewhere else and copy paste it in the title box, which is also a burden and sometimes I prefer just not to post.

Is there something that can be done about this? Note that I never encountered this problem in Sync for Reddit, back in the days.

Other info :

SwiftKey version 9.10.26.30

On Android version 14

Phone : Google Pixel 4A.

Thank you!

19 points · 6 comments · view on lemmy.world

6 Comments

d3Xt3r@lemmy.nz · 5 pts · 2y

SwiftKey user here, can confirm.

A related bug is not being able to access SwiftKey's toolbar, so you're unable to access the clipboard manager or any other advanced features/settings.

can@sh.itjust.works · 4 pts · 2y (1 reply)

I've had this issue forever and it's painful. I just draft my titles out in the body.

Trollivier@sh.itjust.works · 3 pts · 2y

Jesus I didn't even think of doing that... Was doing it in another app.

lemann@lemmy.dbzer0.com · 3 pts · 2y (1 reply)

Does the issue persist on another swipe keyboard too, like gboard or florisboard?

For me, swipe typing in Florisboard is showing the full word in the title box when creating a new post, as expected

pixelscience@sh.itjust.works · 3 pts · 2y

Gboard working fine here.

Trollivier@sh.itjust.works · 1 pts · 2y

BUMP. Is this something we can expect a fix for eventually?