Meta Stack Exchange is where users like you discuss bugs, features, and support issues that affect the software powering all 158 Stack Exchange communities.

What is meta?
Here's how it works:
  1. Any Stack Exchange user can ask a question
  2. The community provides support, votes on ideas, and reports bugs
  3. Your voice helps shape the way Stack Exchange operates

Hi, I just lost a comment entry that was over 600 characters long when I attempted to save it.

Granted, I did not pay attention to the visible character limit. Still, perhaps SO could display a message instead of losing my entry ?

share|improve this question
I agree that this is a bug. But then: 600 characters just for a comment? The world now learns to communicate with 140 char messages (Jeff's beloved twitter, short messages), so this seems so 90ties ;-) – malach Aug 10 '09 at 14:19
@Ralph: have you seen Jeff's beloved twitter feed? That's not communication, it's a sig file! – Shog9 Aug 10 '09 at 14:30

I think the best solution would be to just have the text field stop accepting input at 600 characters.

share|improve this answer
They tried this once. It was very annoying. The bug here is that the Add Comment button still submits after warning you that you're over the limit... – Shog9 Aug 10 '09 at 14:14

This has been fixed and will be in the next build.

I'll refactor that a bit later to follow the same convention that minimum length checks use: disable the submit button if validation isn't met.

share|improve this answer

It does display a message. Unfortunately, it also reloads the page, losing anything you've written. Note that comment submission normally happens via an AJAX request and does not reload the whole page.

That's a bug.

share|improve this answer

Like Thomas said, the system should probably just have that hard limit set. But also, users need to pay attention when the red text starts counting down.

share|improve this answer

You must log in to answer this question.