[ot]Hey nice site! Big improvement, to be sure…about the Rubik’s Cube thing…are you the 2nd guy (LTR)? Also, you should add a slight transparent-to-black gradient to fix up the edge of your bg image. (Or don’t - not my site)
About the article…did Paul really “invent” that? Ten bucks says he didn’t. Let’s all worship at his altar if he did.[/ot]
Wow. So this was only invented maybe 6 months ago? What did people do before that? It’s amazing that it hadn’t been discovered in 10 years…did someone at the W3C confirm that this was how it’s supposed to be done?
I was never taught anything about forms, so this is my very first try. I looked at a bit of the Sitepoint Reference and Fancy Form Design (book).
I’m sure there are problems. Mind finding them (and explaining, if you please)?
Note: Please move this thread if you feel the need to. Sorry.
The label needs a for=“” attribute eto go with the <input> it’s matching with. You shouldn’t need those <br>'s but it’s not a dealbreaker. If you have an input with ID=“city” the label needs to be <label for=“city”>
The article I linked to was from 2005—when the overflow method was first aired.
Make sure to include the for=“” attributes on the labels that Ryan mentioned. Breaks are OK to use if you want to on something like this. You have more control with CSS, but it makes some sense to use breaks, as they work even if CSS is off.
You are better off using a <textarea> element for the message field. Text inputs are really for small amounts of text, like a name etc. If you stick with what you have, you can’t re-use this code on the message input:
Yeah, that’s what I was thinking - I’ve used textareas before, but I couldn’t find any examples of it being properly used. I want my textarea to be multiple rows and columns. I presume that the “rows” and “cols” attributes haven’t been deprecated?