You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
As soon as I post one answer (the first always works fine), the following answers will not work as I always get the following script's error in the console:
Uncaught SyntaxError: Unexpected token h in JSON at position 149
at Object.parse (<anonymous>)
at Function.parseJSON (lia-scripts-common-min.js:32)
at Object.success (thread-reply-field.min.js?sha=2814745:2)
at fire (lia-scripts-common-min.js:55)
at Object.fireWith [as resolveWith] (lia-scripts-common-min.js:60)
at done (lia-scripts-common-min.js:494)
at XMLHttpRequest.callback (lia-scripts-common-min.js:547)
at XMLHttpRequest.nrWrapper (1308564:3)
I have tested on Chrome and Safari, used different sessions and the result is always the same. Even if I logout and login again it is not working. Except from the console, nothing is showed to explain the error.
Can you confirm with what Matthias said, if you're still having the issue today, and only yesterday? What is the exact behavior in your browser UI when this occurs?
Secondly, Are you having difficulty answering any questions at all, or only specific ones? Does this happen no matter which device you use (another computer, phone, etc.)?
Thank you for sharing that video. It's very helpful!
In this case, you're replying to an answer, so it might not trigger the same behavior. If you were to reply instead in the Suggest an answer field, does the issue occur?
Hi Shannon, yes it occurs... in the following video capture I was able to replicate the strange behavior:
You can find the video here (with real life sounds behind hihi).
Thank you for sharing that. The team has been looking into this, and so I'll share your most recent example with them now. I'll let you know if I find out anything about this issue.