div.fieldset (1-quest. containers)fieldsetf_basic_radioSet, f_basic_text, f_basic_textarea, f_basic_select fieldset (multi-question containers)fieldset would map to the question builder anmes probably (e.g. fieldset.eyeColorPicker)div) for a set of questions or a single questionlegend element.div.fieldsetDescription after the legendstyle="display:none") if they are conditionally dependent on another questions answer.fieldsets. textarea, radio etc.) requires at least one className of field. This is to enable the highlighting of the parent fieldset (if we use the Wufoo model for highlighting). TBD if radios/checks need the class of fielddiv or span and is floated by default. These elements may or may not have classNames.cols or size attributes). However, a class name can be added to any form input or other markup element to change its inherent width. (These may be applicable to containing divs and spans as well (TBD). Right now, the running ones are here (fw = formWidth)
.fw_s = 1/3 * width(.fw_l).fw_m = 1/2 * width(.fw_l).fw_ml = 2/3 * width(.fw_l).fw_lclear rules in the CSS for that particular fieldset or question type. For example, if we have :
<fieldset class="responsibilityCheck">
<div class="f_datePicker"></div>
<div class="f_basic_textarea"></div>
</div>
...then normally the datepicker and textarea would be side by side if the column-width allowed them to be. However, we might use .responsibilityCheck div {clear:both} to make the questions stack vertically .
legend - describes a set of input/label pairs or a set of fieldsets.fieldsetDescription - longer, prose description to accompany the legendspan.fieldError will contain error-handling at a field-level of specificity. Positioning of this balloon will be based on Nosal's JS work ;-) The markup/content for the error must render inside the label element (see question 3. on this page.). Events that generate an error need to also move the cursor (e.g. location.hash('error_question1b')) to the right place.span.fieldError should now come before the span.formTipspan.formTip - this, like the span.fieldError, also needs to render inside the label element. Another container element, span.cont_tips encapsulates both of these elements and is a child of label.span.cont_tips - these can be placed inside label or legendspan.mask) are optional. We will include the mask as part of the regular label text.p.preFillTrigger) will contain a checkbox input and label. probably will live immediately prior to a textarea and will take contents from one textarea and prefill them into another question.p.duplicateQuestion) TBD. probably will live immediately prior to a textarea and will take contents from one textarea and prefill them into another question. Will live at the end of a question-containing divtitle attr. will need to be filled out in order to maintain label/input integrity. See .fset5, the large matrix questions example. Whlie I used a shorthand title, it would be acceptable to repeat the entire contents of the thead's th value in the title attribute.