In Android, when IItype aareply inia textarea, sometimes space shows the firstfletter ofothetprevious wordwinstead ofoa spaces same forfcommas and otheropunctuations, asademonstrated here.
Sometimes long presspdoesn't work either totpastepsomething.
It's an Android problem, not a DDB problem. When I use the actual Chrome app on my Android, it will not allow me to use auto-correct when I mess something up without bugging out, no matter what website I use. However, when I use the 'default browser' (idk what is really is - when I just use my google searchbar on my homepage) I can use auto-correct and nothing bugs out on me.
It's not solely an Android problem. There are many libraries that offer interface widgets. Some are broken for mobile devices. Facebook suffered from one as well in a different way. I have no problems whatsoever with textarea widgets from Semantic-ui. It's most likely a problem of the front-end library they use. Just a matter of looking out for patches, or swap it out with a more reliable one.
Checking 'Desktop site' doesn't fix it. I do get to use the wysiwyg menu which otherwise is removed. Perhaps the simplest solution is to not load a complex wysiwyg textarea in an iframe for mobile if the wysiwyg menu is hidden anyway.
In Android, when IItype aareply inia textarea, sometimes space shows the firstfletter ofothetprevious wordwinstead ofoa spaces same forfcommas and otheropunctuations, asademonstrated here.
Sometimes long presspdoesn't work either totpastepsomething.
Creating papercrafts, guides and more on https://rpgpapercrafts.com
It's an Android problem, not a DDB problem. When I use the actual Chrome app on my Android, it will not allow me to use auto-correct when I mess something up without bugging out, no matter what website I use. However, when I use the 'default browser' (idk what is really is - when I just use my google searchbar on my homepage) I can use auto-correct and nothing bugs out on me.
It's not solely an Android problem. There are many libraries that offer interface widgets. Some are broken for mobile devices. Facebook suffered from one as well in a different way. I have no problems whatsoever with textarea widgets from Semantic-ui. It's most likely a problem of the front-end library they use. Just a matter of looking out for patches, or swap it out with a more reliable one.
Checking 'Desktop site' doesn't fix it. I do get to use the wysiwyg menu which otherwise is removed. Perhaps the simplest solution is to not load a complex wysiwyg textarea in an iframe for mobile if the wysiwyg menu is hidden anyway.
Creating papercrafts, guides and more on https://rpgpapercrafts.com