You should really style form fields with CSS rather than rely on the size attribute. You can set the max size of a form field by passing the max length value into the constructor
Max length is not the same as the size attribute, though, and are, in fact, two completely different attributes. The size attribute in HTML form fields defines the physical size, in pixels (or in a couple of cases, in visible characters), of the field itself. It has nothing to do with the number of characters the field can hold (as is the case with "maxlength"). (On a side note, why the HTML spec uses "size" and not "width" is beyond me.) More information on the "size" attribute of HTML fields can be found at W3Schools. Now, I did happen to stumble on information that shows that the "width" CSS attribute does, in fact, work (or at least is supposed to) on the form fields, which more or less renders my current problem in that regards moot, however, it doesn't change the fundamental misunderstanding of "size" vs "maxlength" and the lack of information on the matter as a whole. As another aside, this did also bring to light that the field IDs of form fields generated from the code have really long IDs...
Well, at least now, it will be somewhere that one should use the CSS "width" style in place of the HTML "size" attribute for fields, since like I said before, there was an unanswered question about it that came up in my own search, and there will inevitably be more people looking.
Also, thank you for updating the documentation about the email thing. One of the things I have noticed is that you guys are really good about listening to people, both on and off of these forums and working to address various issues. Good customer service is, sadly, an increasingly rare thing, so keep up the good work. :)
I guess some more examples of the various API features would be good.
One of the pitfalls I've found in community software projects in general is that they tend to be fantastic for really basic users and powerful for advanced users, but leave the intermediate ones somewhere in Limbo. In the case of SS, as an intermediate developer, the API documentation, while certainly thorough and probably useful to those more knowledgeable than I, is a step away from Greek to me. It's basically like "I know it has $Attribute, but how do I access it to make it do what I want?" and, unfortunately, that level of example seems to be missing (and that goes for more than just SS, as I previously mentioned).
Finally, I still can't seem to get template logic working in my email templates. It works great until I try to add the following:
<% if $From != firstname.lastname@example.org %>
<p>Text to appear only if the email isn't the default From in the event of an empty field (as set in _config).</p>
<% end_if %>
From what I can gather of the information I've been able to find on template if blocks (which has been pretty much limited to the Template doc, other examples that use logic only have "if $property"), I think the syntax is right, but it doesn't successfully send the email. If I should be able to use such template logic in email templates, what am I doing wrong/missing (it works without the if block)?