otwcode/otwarchive — pull request #1287 by sarken (2013-07-23 04:38:24+00:00)
Title: Issue 82 LiveValidation JavaScript errors make everything else on the page shift

http://code.google.com/p/otwarchive/issues/detail?id=82

This applies `position: absolute` to the LiveValidation error messages that pop up before you submit forms (as opposed to error messages that happen after you submit). This takes the error out of the page flow so the other elements on the page don't shift around, which was annoying people.

* The HTML on the Support and Abuse forms was incorrect (the LV was inside the `dl` but not inside the `dd`); this fixes that and places the LV directly beneath the field it applies to, so it's the same as all the other fields that have LV.
* Add a few translation strings to the Abuse form.
* Adds the `required` class and the * we use to indicate required fields to some required fields that were not properly labeled.
* Removes the colons from the fields on Support and Abuse, since we're shifting away from them.
* Fixes the tab spacing in Support form file.
* We've started applying `required` to the `dd` containing the field that is required (see: the Fandom field on the work form). This was also turning footnotes and other notes red. Adding `dd.required { color: #2a2a2a; }` stops that.
* Rearranged CSS in the modal styles to match our formatting standards (CSS3 properties last and double-indented, selectors all on one line, properties on their own lines).
* `.character_counter span` was set to a specific width, which would cause the number to run into "characters remaining" message if you ran over by tens or hundreds of thousands of characters.

There are two known issues here:
* In webkit browsers, on the Abuse form's "Link to the page you are reporting (required)" field and the Support form's "Your comment (required)" field, the LV error pops over the field if you click in the field, leave it empty, click away, click back in field, and click away again. This is because of the float on the footnote. I might do a complete overhaul of footnotes on forms when I attempt to beat the forms into submission, but for now? Just don't do the thing that causes the bug. (It's cosmetic, you can still select the field, it's not easily fixable.)
* When you are logged in as an admin and you go to suspend a user, if you enter something that isn't a number in the "Suspend: enter a whole number of days" field, the error message doesn't point directly at the box, but at the radio button for the "Suspend: enter a whole number of days" option. That's because we don't normally lay our forms out like that. Talk to me after the form standardization of doom.