Changes for page Forms Standards: Vertical Layout

Summary

• Page properties (2 modified, 0 added, 0 removed)

Details

Page properties

Author

...	...	@@ -1,1 +1,1 @@
1		-XWiki.enygma
	1	+XWiki.mflorea

Content

...	...	@@ -14,7 +14,7 @@
14	14
15	15	== A. Usage ==
16	16
17		-* Obs: The CSS classes have as parent the ##.xform## class. This is supposed to be used on the form tag, but if the styling is done inside dynamically generated structures it can be used on other elements, like divs, as long as the element remains the parent for the other form components. For instance, a common use case is when you design a form that is to be used in inline edit mode, you have to wrap it in a div element and use ##class='.xform'## on the div instead of the form. This is needed because in inline edit mode your form element will not be rendered and, instead, your page will be wrapped inside the main inline edit form.
	17	+* Obs: The CSS classes have as parent the ##.xform## class. This is supposed to be used on the form tag, but if the styling is done inside dynamically generated structures it can be used on other elements, like divs, as long as the element remains the parent for the other form components. For instance, a common use case is when you design a form that is to be used in inline edit mode, you have to wrap the form content in a div element and use ##class='.xform'## on the div instead of the form. This is needed because in inline edit mode the entire page content is put inside a form element to which we don't have access as it is generated in a velocity template, and generating a form element inside the page content will produce invalid HTML since nested form elements are not allowed (the inner form element will probably be removed either by the rendering engine or by the browser).
18	18
19	19	(% summary="Table containg classes for different form components" %)
20	20	|= Tag |=Type |=Size |=Classes | | |=Usage\\