Comment On Thank You for Enabling JavaScript!

rocco:

"thank you"

rocco:

attempting the dreaded comment, i got:

Not sure what it was, but it was logged. A human will eventually look at it. If the problem persists, please Contact Us. If the problem is on the contact form, then ... well ... that pretty much sucks. You can email instead: alexp-at-WorseThanFailure.com.

Carl:

The function is horribly mis-named, but the author doesn't seem to think that's a very big deal. So the WTF is using Javascript to perform input validation? Lame.

toth:

Maybe I'm a moran, but I don't see the WTF here. Maybe that means I'm TRWTF.

Farmer Innes-D'en:

TRWTF is that anybody assumes client-side Javascript to have done any validation for them. No, really. Page one, people, page one.

<form method="post" action="process.php">

<input type="button" onclick="this.form.submit();">

</form>

NetBen:

This is a WTF if this is THE only user input validation.

This is NOT a WTF if this function is part of enhancing user experience.

Both factors unknown, so useless article.

JuanCarlosII:

Carl:

The function is horribly mis-named, but the author doesn't seem to think that's a very big deal. So the WTF is using Javascript to perform input validation? Lame.

You don't seem to understand. Using JavaScript for anything at all is wrong because someone might not have it enabled.

Neville Flynn:

This is not a WTF unless you add this sentence to the article: "Oh, and they don't perform validation on the server."

By the way, would that JS stop someone from pasting in invalid text? Or does it only work if the user manually types in invalid text?

akatherder:

Farmer Innes-D'en:

TRWTF is that anybody assumes client-side Javascript to have done any validation for them. No, really. Page one, people, page one.

Then make sure they have javascript.

<form method="post" action="process.php">

<input type="button" onclick="this.form.submit();">

</form>

Unicode:

Thank you for properly supporting me. ಠ_ಠ

NetBen:

This is a WTF if this is THE only user input validation.

This is NOT a WTF if this function is part of enhancing user experience.

Both factors unknown, so useless article.

dkf:

NetBen:

This is a WTF if this is THE only user input validation.

This is NOT a WTF if this function is part of enhancing user experience.

Both factors unknown, so useless article.

Oh, it has plenty of WTF!s in it even without knowing whether it is the only validation.

My favourite that I've seen so far is that bit with checking if it's processing decimal and, if so, comparing to see if the key was a period. When that character is a member of set of chars checked for previously. Thankfully, the test wouldn't lead to an observable outcome anyway, since it's just choosing whether to return false, or to instead return false. Vital decision, that…

(Yes, there's a focus change in there. Anyone want to bet which element would be focused on at that point?)

Anonymous:

akatherder:

Farmer Innes-D'en:

TRWTF is that anybody assumes client-side Javascript to have done any validation for them. No, really. Page one, people, page one.

Then make sure they have javascript.

<form method="post" action="process.php">

<input type="button" onclick="this.form.submit();">

</form>

What if I call process.php with my own POST variables? :)

Adam:

I:APOSTROPHE:ve had the misfortune to have to fill in a problem:HYPHEN:description form for
<...clip...clip...>
stopped giving :QUOTE:Illegal character:QUOTE: errors. Is this typical:QUESTIONMARK:

John C. Random:

JuanCarlosII:

Carl:

The function is horribly mis-named, but the author doesn't seem to think that's a very big deal. So the WTF is using Javascript to perform input validation? Lame.

You don't seem to understand. Using JavaScript for anything at all is wrong because someone might not have it enabled.

To take that to its logical conclusion, writing software at all is wrong, because someone might not use it.

Farmer Innes-D'en:

TRWTF is that anybody assumes client-side Javascript to have done any validation for them. No, really. Page one, people, page one.

Anonymously Yours:

John C. Random:

JuanCarlosII:

Carl:

The function is horribly mis-named, but the author doesn't seem to think that's a very big deal. So the WTF is using Javascript to perform input validation? Lame.

You don't seem to understand. Using JavaScript for anything at all is wrong because someone might not have it enabled.

To take that to its logical conclusion, writing software at all is wrong, because someone might not use it.

This is a perfect example of why using sarcasm is wrong. I hope you learned something from this, JuanCarlosII.

akatherder:

Farmer Innes-D'en:

TRWTF is that anybody assumes client-side Javascript to have done any validation for them. No, really. Page one, people, page one.

Then make sure they have javascript.

<form method="post" action="process.php">

<input type="button" onclick="this.form.submit();">

</form>

Mark Bowytz:

Now, before bashing the function for it's curious name...

akatherder:

Anonymous:

akatherder:

Farmer Innes-D'en:

TRWTF is that anybody assumes client-side Javascript to have done any validation for them. No, really. Page one, people, page one.

Then make sure they have javascript.

<form method="post" action="process.php">

<input type="button" onclick="this.form.submit();">

</form>

What if I call process.php with my own POST variables? :)

You would be fine or you would get a syntax error. If you're fine, my job is done. If you get a syntax error, then you don't know what you're doing.

tetsu:

It purports to return True or False depending on if the characters... It's a boolean utility function that changes the state.

Jonathan Collins:

akatherder:

Anonymous:

akatherder:

Farmer Innes-D'en:

TRWTF is that anybody assumes client-side Javascript to have done any validation for them. No, really. Page one, people, page one.

Then make sure they have javascript.

<form method="post" action="process.php">

<input type="button" onclick="this.form.submit();">

</form>

What if I call process.php with my own POST variables? :)

You would be fine or you would get a syntax error. If you're fine, my job is done. If you get a syntax error, then you don't know what you're doing.

Ever heard of SQL injection?

Fedaykin:

Data scrubbing to avoid SQL injection = WTF

ICOLONCOLONCOLONAPOSTROPHECOLONCOLONCOLONve had the misfortune to have to fill in a problemCOLONCOLONCOLONHYPHENCOLONCOLONCOLONdescription form for a COLONCOLONCOLONOPENBRACKETCOLONCOLONCOLONmajorCOLONCOLONCOLONCLOSEBRACKETCOLONCOLONCOLON consumer hardware manufacturer that, while asking for a complete report on why I wanted them to repair my laptop, forbade COLONCOLONCOLONOPENBRACKETCOLONCOLONCOLONserverCOLONCOLONCOLONHYPHENCOLONCOLONCOLONsideCOLONCOLONCOLONCLOSEBRACKETCOLONCOLONCOLON almost all nonCOLONCOLONCOLONHYPHENCOLONCOLONCOLONalphanumerics COLONCOLONCOLONDASHCOLONCOLONCOLON the procedure was apparently just to keep removing characters until it stopped giving COLONCOLONCOLONQUOTECOLONCOLONCOLONIllegal characterCOLONCOLONCOLONQUOTECOLONCOLONCOLON errors. Is this typicalCOLONCOLONCOLONQUESTIONMARKCOLONCOLONCOLON