pull down to refresh

22 sats \ 7 replies \ @sox 11h \ parent \ on: SN release: what you see is what you get (wysiwyg) editor meta

I'm investigating this now, can I ask you which keyboard are you using?

write
compose
101 sats \ 6 replies \ @Taj 11h

Samsung default.

(Used foss heliboard and works fine)

reply
22 sats \ 5 replies \ @sox 11h

I see, I don't have a Samsung device right now but I'll find a way to get that keyboard and find a fix.

The problem (or the advantage, perspectives) on Android is that every keyboard can have their own IME[1] implementation, leading to bugs almost always unique to each keyboard. We're doing great efforts in trying to squash them all because we care and we're not easily comfortable in asking people to "just use another keyboard".

  1. IME is what controls autocorrect and characters that need to be composed like Japanese ones ↩

reply
101 sats \ 2 replies \ @0xbitcoiner 11h

This looks like the cursor blinking. I'm on the Brave browser on PC.

reply
33 sats \ 1 reply \ @sox 11h

Welcome to virtual cursors! Browsers can't normally land a cursor in "non-editable" elements, but everything in compose mode is editable ... so we fake a cursor!

It can be pretty janky and to make it less janky we implemented a way to insert a paragraph if you click at the top or bottom side of an element. Let us know if you encounter any issues or odd behavior!

reply
101 sats \ 0 replies \ @0xbitcoiner 11h

Oh! cool

reply
104 sats \ 1 reply \ @Taj 11h

I see 👀

I guess i could go back to a keyboard from zapstore

But i find them over customizable and I end up over complicating and cluttering the keys 🔑 😒

When I'm constructing a post, I write it out in standard notes app and paste it in

reply
22 sats \ 0 replies \ @sox 11h

The most compatible keyboard so far is Google Keyboard (Gboard), you can try that, if you'd like, while we prepare a fix for your Samsung Keyboard.

reply