Pretty minor bug, I guess... but it caused me to waste a half hour yesterday while dealing with another issue, since I was under the impression that the comment was right and the code was wrong, but in fact it was the other way around ;)

(Seems like what's going on here is actually a bit of a technical limitation in FAPI, though? Just because the form has errors doesn't mean the user doesn't want to hit the "Save" button after they correct them.)

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

Anonymous’s picture

Title: Fix incorrect code comment in comment_form() » Fix incorrect comment for comment_form() in comment.module
Priority: Normal » Minor
Status: Needs review » Reviewed & tested by the community

Documentation patch only. Review of changes look good to me.

Dries’s picture

Status: Reviewed & tested by the community » Fixed

Committed to CVS HEAD. Thanks.

Anonymous’s picture

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for two weeks with no activity.