Don't know about him... .but default keyboard. And once more, it ONLY occurs here, not on my site, TAZ or any other XF site I use.16.1 is the latest
Maybe you’re using 3rd party keyboard? Swift or Gboard maybe?
Is it serving the old version from your browser cache? It resets less often on mobile than it does on desktop.Strange. We did roll out a Froala update which explains why it is only here but it’s not something I can reproduce myself. Using iOS 16.2 Beta on iPhone 12.
Anyone else got 16.2 Beta?
Was my first thought and I cleared the entirety of Safari's cache.Is it serving the old version from your browser cache? It resets less often on mobile than it does on desktop.
…and backspace works.Froala update reverted.
![]()
I never noticed that myself and it doesn’t seem to be happening to me now if it’s something that’s consistently reproducible (on a 13 Pro Max w/ 16.1).@digitalpoint have you ever had, or do you still have an issue where if you finish a sentence on iOS, then hit return twice, the keyboard isn't auto capitalizing like it should?
Traditionally I have to hit return 3 times for it to work, and it still only puts in the correct number of new lines.
This was supposedly fixed and I believe, to many, it was. But for me it never was. And now I didn't get the iOS backspace issue either. So it's like my editor is stuck on some past version.
Just tried it on two other sites and it's fine.I never noticed that myself and it doesn’t seem to be happening to me now if it’s something that’s consistently reproducible (on a 13 Pro Max w/ 16.1).
Definitely really weird what’s going on with your device. Probably a dumb question, but do you have an iPad or even an iOS simulator in Xcode to verify it’s something specific with that device?
FroalaEditor.VERSION = 4.0.10
on my iOS device. But if you are seeing that carriage return issue, maybe you are on a completely old/unexpected version somehow? And if that's the case, firing up developer mode on a Mac that your phone is connected to would probably be helpful so you can inspect things like HTTP requests.Honestly, I'm praying and hoping for someone to hint at something stupid I might have missed and if someone does I'd be thankful.It does seem pretty strange that it seems like you are getting a different version of JavaScript on your phone somehow. I've skimmed through a few things I'm able to check on this end and everything looks normal. For example xenforo.com has Caching Level properly setup so XenForo's cache breaking is working properly.
Is Froala the expected version on your iPhone? For me,FroalaEditor.VERSION = 4.0.10
on my iOS device. But if you are seeing that carriage return issue, maybe you are on a completely old/unexpected version somehow? And if that's the case, firing up developer mode on a Mac that your phone is connected to would probably be helpful so you can inspect things like HTTP requests.
Maybe an issue where you have dev mode enabled just for you here and there's a problem with the non-rollup/compiled versions of JavaScript that us normal people don't see since we aren't in dev/debug mode?
You're no dummy, so I'm probably telling you stuff you already know....just spitballing here.
We use essential cookies to make this site work, and optional cookies to enhance your experience.