Styling a Form with CSS Module

First: thread:379
Feedback from naive user
Edited: 26 Oct 2011 12:41 by: Sheepdog
Comments: 3
Tags:

««

« default property for wiki field
« why does %%form_data{variable}%% render in its own <p> block?
« editor buttons for wiki-type-form-field
« consistent width
« replicate the page-edit experience
« Static Wiki Field Type
« Recommended Documentation Changes
« Static Fields
« 'editable' property (all field types)
« Hint Text

Previous: thread:337
Hint Text
Edited: 22 Mar 2010 18:16 by: (user deleted)
Comments: 17
Tags:

Last: thread:141
Which aspects of this design do people want first?
Edited: 11 Nov 2009 12:44 by: leiger
Comments: 14
Tags:

»»

Data form 'required' property UI design »
useful form data »
wiki fields should support the same features as a page that doesn't use data forms »
Long term ideas »
Field values depending on previous field »
Date fields »
Will this lead to a semantic wiki? »
Displaying the page title in the form »
Attribute for page-title »
Attribute for page-title »

Next: thread:290
Data form 'required' property UI design
Edited: 18 Mar 2010 09:05 by: leiger
Comments: 3
Tags:

Ed Johnson wrote on 22 Mar 2010 16:25

As I continue to work with form styling, I discovered that you can't use [[module css]] on the form _template page if you want to apply the styling to a new page. This is obviously a result of the page not actually existing until is is saved. Once saved, the module's styling works fine. It will be great if the autosave wish is implemented to get around this issue.

Has there been any discussion or a design written up for autosave? The only references I find are the wish with no comments and James' mention of it here.

Until then, if you want CSS styling to work on a data form when creating a new page, be sure to put the CSS in your main custom CSS code.

-Ed

Start a new sub-thread

Comments: 0