Improve HTML/DW markup cleaner handling of comments

[pauamma]

Title:
Improve HTML/DW markup cleaner handling of comments

Area:
comments

Summary:
If a comment contains incorrect HTML or DW (or LJ) markup, the commenter should be returned to the comment form with an error message, instead of getting the comment posted with bad markup. Also, the error message should be specific, instead of mentioning "entry" and "owner".

Description:
See summary. Note: ideally, this might make on-display cleaning unnecessary, but comment importing from other sites (as part of journal importing, cross-posting, or cross-reading), or comment submission by email, clients, or other means may make that unworkable in practice.

(This is equally true of entries, but everyone can edit their entries, but some users can't edit their comments, which makes it more important to spot the bad markup at submission time instead of render time.

Poll #2592 Improve HTML/DW markup cleaner handling of comments

Open to: Registered Users, detailed results viewable to: All, participants: 51

View Respondents

This suggestion:

View Answers

Should be implemented as-is.
49 (96.1%)

Should be implemented with changes. (please comment)
0 (0.0%)

Shouldn't be implemented.
0 (0.0%)

(I have no opinion)
2 (3.9%)

(Other: please comment)
0 (0.0%)

Comments

[cesy]

I vaguely remember seeing this talked about before somewhere.

[afuna]

Hmm, there was a suggestion for a bad markup warning to happen when you post an entry. (Though it wouldn't have prevented the entry from going through). That might have been what you're thinking of.

[cesy]

Ah, possibly that's it, yeah.

[melannen]

Relatedly, there should be some sort of warning that html links don't work in anon comments.

[denise]

There is now! With the last push.

[auroraprimavera]

Awesome!

[auroraprimavera]

I would really like to have this - as of right now I can't edit my comments and sometimes I miss a thing or two when it comes to markup. Would make things a lot easier for me.

[musyc]

I would like some form of highlight indicating specifically where the error was thrown. I've run into a couple of situations where I've posted several identical lines/paragraphs/etcs and missed one lousy " that throws off the whole thing. Having to skim each and every line because they only differ by a filename or such is an exercise in frustration.