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
I have been trying to answer on the community from three browsers - Chrome, Firefox and Edge.
Every time, I write the answer and I hit on the Answer button, the button goes disabled and the answer is not posted.
Has anyone encountered this ? How do I fix this ?
I also have the problem occasionally.
In that case, I copy my answer, close the respective thread and open it again. Then I copy my answer into the text editor again. So far, this has mostly worked.
The editor also seems to have some problems with certain characters. It is also important that the code of any kind is always shown in the code block
I had this behavior too, sharing what happen with me:
I know of one way to replicate exactly these sypmtoms - get distracted.
If you open an community question in a browser and then wander off to make tea or something, when you come back, you can get exactly what you describe. Click answer or comment and it just goes grey and posts nothing. Refresh the page and post again - absolutely fine.
It feels like there is an invisible timeout on an open page. It's not logging you out, but it is blocking posting if you have been inactive.
Is that what you are seeing here?
Thanks for the response, @Nic Brough -Adaptavist- .
I wish you were right :)
Even if I refresh the browser or open a fresh new browser or a tab (Edge, Chrome, Firefox) with no time lag absolutely, the behavior is the same. The Answer button goes grey. Surprisingly, I can still click on Cancel button.
Is there anything else I can try?
I experience the same behavior that Nic mentions; copying my reply and refreshing the page with CMD+R has always solved it. I'm not sure on why that might not have worked for you, so we need to look into that more.
I've just reported his with the team, so hoping to get some clarity on this!