nostr:npub1syjmjy0dp62dhccq3g97fr87tngvpvzey08llyt6ul58m2zqpzps9wf6wl This is what it looks like if I try to use the text input in jumble.

social to report the issues with the text input without waiting for it to catch up with each bit I've typed

-

w

hich I should never have to do, because this is a flagship phone made in the past year and jumble is competing

with nothing at all for system resources. It's caught up part of the way to what I'm typing now and I see how it randomly added like breaks in the middle of something, classic issue. And there it goes changing "line" to "like" for the nth time today (which I know was t me because it's happened multiple times, and with the screen lagging, my focus is directly on watching which buttons I press on my keyboard and carefully paying attention to backspace exactly once and fix it when I mistap)

Web browsers simply aren't ready for whatever you're trying to do, there are all kinds of code things in JavaScript of whatever that you can experimentally use to mess with your u

Reply to this note

Please Login to reply.

Discussion

sers by doing extra stuff in the text bo

xes, but if the goal is to help users do anything, it does not work because that code is so heavily experimental. I don't know why it never gets fixed but it's been like this the whole 25 years or so I've been using web browsers: there are plain text input boxes that just work, and then there are "JavaScript enhanced" input boxes that never ever ge

t past waiting for a powerful enough CPU, or e

nough bug fixes,or whatever it would take to have more than a plain text box and not break anything

"or whatever" changed to "of whatever"

It's obviously malicious of Google to program gboard to make mistakes like that when there's lag. There's no reason lag should add changes that wouldn't normally happen. Obviously Google's fault

But web devs should also not be using broken JavaScript code to make the issue come up

(I waited for it to catch up typing that last add-on comment, it isn't merely right by chance)

That’s just your keyboard’s auto-correct. You can probably disable it in the settings.

No, and I already pre-emptively responded to this, but I'll respond again. My keyboard's auto-correct does not use so much CPU that it lags itself out and causes itself to make additional errors in a plain text input box. JavaScript text input boxes cause that, not keyboard autocorrects.

And autocorrect does not randomly add line breaks.

Text input has been the main issue with jumble the whole time I've used it, please just give us a plain input box

It could be some other part of the page's javascript, I just assume it's directly related to the text input box based on experience with these issues changing when text input boxes change (across all of my web user history)

There is indeed a resource usage issue, since a large amount of data needs to be fetched and processed, I’m doing my best to optimize it.

As for the text input box, I’ve barely added any extra functionality to it and there’s no text replacement involved, so I don’t think that’s the cause.

Whatever it is is very sporadic but very ongoing once it happens - won't stop until a phone reboot or full closing and relaunching of tabs+browser

Hope that helps, if it's not input box related 🤙

I'll keep an eye on it 🫡

There's definitely way too much JavaScript interference in the text input box

It doesn't even handle copying and pasting correctly at all - for example, it removes line breaks from anything pasted into it, but multiplies extra line breaks into anything copied from it

Received

This happens because Tiptap doesn’t treat multiple `

` elements as separate paragraphs by default, which makes it seem like line breaks are being removed. I’ve added some handling during paste that should help avoid this issue.

Thank you 🙏

Thanks for your feedback, too 🫡