␡
- BRINGING IN SEPARATE PARAGRAPHS FROM WORD
- FOCUS YOUR ATTENTION RIGHT HERE
- WATCH OUT FOR KILLER OCTOTHORPES
- HEADING THIS WAY
- RESCALING AN IMAGE IN DREAMWEAVER
- QUICKLY CLEARING A PAG
- FINDING YOUR ASSETS IN A DARK ROOM (WITHOUT A FLASHLIGHT)
- EVERYBODY, COME ON AND DO DA COMBO, MON!
- CLOWNS TO THE LEFT OF ME, JOKERS TO THE RIGHT...
- ZIPPY FORM ORGANIZATION WITH THE FIELDSET TAG
- WHERE, OH, WHERE HAVE MY WINDOW SIZES GONE?
- STAYING IN GOOD FORM
- PLAYING NICE WITH THE INSERT BAR
- "A" IS FOR ACCESSIBLE APPLETS
- MULTIPLYING RADIO BUTTONS
- FANCY-SCHMANCY FORM BUTTONS
- LABEL-LICIOUS
- BUTTON, BUTTON, WHO'S GOT THE BUTTON?
- ANCHORS AWAY
- BYE, BYE HELPER TEXT
- THAT'S WHAT IT'S ALL ABOUT
- JAVASCRIPT REQUIRED
- TRANSFERING SITES
- NO MORE BROKEN LINKS
- REUSABLE JAVASCRIPT
- VIEW AS ROOT
- INITIALLY SELECTED VALUE
- REQUIRING INPUT
This chapter is from the book
This chapter is from the book
This chapter is from the book
This chapter is from the book
STAYING IN GOOD FORM
Naming conventions are extremely helpful in avoiding common form-processing errors. The trick is to create unique labels for form elements that are instantly identifiable to the developer. My technique is to combine the type of form element with its purpose. For example, I would call a text field for accepting the name of a country countryText—whereas a list element for the same purpose would be countryList. I use mixed case (also known as intercapping) to avoid spaces—a definite no-no in web naming—but this helps keep it legible.
){kind=small}
Figure
7.10