What's the point of having a limit. The description should be as long or short as it takes to provide the proper guidance. Only humans can judge that. Nannyware imposing arbitrary min and max lengths doesn't increase quality.

My point was that there is a counter and it isn't working. If we decide it is not needed, it should just be removed from the UI and avoid useless clutter. I have no strong opinion about that.

I could see a potential merit in that limit, though. Since the guidance text goes in a pop-up maybe there would be usability problems if the text is too long. If HTML standard allows "wrapping" pop up text, that would be a no-issue. However if a pop-up always shows up with the full text in view this could cause problems, especially on portable devices with small screens. I have no knowledge in modern web programming, so I'm just wild guessing here.

There's always going to be some limit, from the database column type if nothing else, but we might need to raise it. In any case, though, yes if we show a counter it should be accurate. Thanks for the report.

I've now realized this is for the short guidance, not the wiki. The wiki should be as long as is needed, but the short guidance is meant to fit in a summary or hover text, so it can't be huge. And I've reproduced the problem in Chrome.