Web Development Ejector Seat - Part 1: Form Reset Buttons
That's right, we're caught in the jet wash and we're going ballistic, Mav. We've got to eject| on second thought, you stay right here Form Reset Buttons. You've lost that lovin' feeling, and I feel the need| the need for you to speedily hit that pavement of waves.
This is the Web Development Ejector Seat. A place I'll visit from time to time to cleanse myself of some element of web development that needs to go down in a death spiral. Today's target: the Form Reset Button (FRB).
For years, I believed the FRB was already decomposing in a landfill or had been flushed into the sewer, but a recent project defibrillated the pesky pest. Oh, how it pained to me write that forbidden code!
Don't know what an FRB is? Let me explain. An FRB is a button whose purpose is to clear all the information the user has just painstakingly entered in the various text boxes, text areas, and other form elements.
Generally, the FRB lies in wait right beside the form's Submit button lying in wait with designs on leaping in front of your mouse cursor when you mean to click the Submit button and instead irretrievably deleting all the form data you spent half an hour entering.
Not that it's ever happened to me. I wouldn't be one to zone out and accidentally hit the wrong button. No sirree!
Statistics gathered from Madeup Stats, Inc. show the FRB has cost the United States alone a cumulative 235 years of wasted productivity. In addition, nearly 2,000 broken keyboards and 750 shattered monitors have felt the misplaced wrath of FRB victims across the country. Psychological and emotional damages are immense, but immeasurable.
But all of that ends today! I can see the plane violently crash into the awaiting ocean from high above on my parachute perch. Farewell, Form Reset Button... you foul villain. You will terrorize the web community no more.
