Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Context Mismatch #37

Open
josiauh opened this issue Feb 16, 2025 · 2 comments
Open

Context Mismatch #37

josiauh opened this issue Feb 16, 2025 · 2 comments

Comments

@josiauh
Copy link

josiauh commented Feb 16, 2025

here we go again.

so... as of writing this you did an event and everything went haywire with people editing so much stuff

and being the annoying pest i am, i spotted the context mismatch error. again.
so i went back to the network tab. first thing i spotted was that the words were shifted by 1. and then i refreshed so i reproduced it, and this sent me down a RABBIT HOLE.

the words were FINE? word index and all, so it HAD to be something internally. clicking a few words AFTER wouldn't result in the error, and im just dhfjhdskfjmcn,mn

and then i did it ONE more time and the words shifted. 4 to the right. and again, the context of the payload was as follows:
{"before":"and [first-class functions](https://bliptext.com/articles/first-class-function)","word":".","after":"It is","index":80}
IT SHIFTED 4 TO THE RIGHT AGAIN?

maybe it's because i had it on for too long. so i refreshed and it didn't happen immediately. then the 3rd time i swapped it shifted 1 to the right. there's so much shifting going on and i have NO idea what's going on.
RAAAAAAAAAAAAAAAGHHHHHH

@creeperita09
Copy link

We have no fing idea either, face is a great developer!

@face-hh
Copy link
Member

face-hh commented Mar 2, 2025

The current context mismatch happens when:

  • Formatted words (**, *, []()) get replaced twice.
  • hello -> **hi** -> wassup -> Context mismatch!

I will leave this be as it's not a super major issue, and is usually fixed with a page reload.

I have tried re-rendering the content when the error happens, but it would require too big of a codebase change to work properly. A full page refresh is better.

@face-hh face-hh changed the title Context Mismatch 2: Electric Boogaloo (REALLY CONFUSING?) Context Mismatch Mar 5, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants