This demo showcases the two different rendering modes of Telerik's ASP.NET Form Decorator: Classic and Lightweight. 	
	
		- 
			Classic rendering is the long-standing rendering mode of the control 				in which its layout is often implemented using table elements. 		
- 
			Lightweight rendering leverages HTM5 and CSS3, 			but the control may lose its rounded corners, gradients and 			shadows in non-modern browsers. With this rendering, table elements in the 			control layout are replaced with generic elements, such as div and span. 		
 		There is also a Native render mode option inherited directly from 		RenderMode. As RadFormDecorator does not have a specific HTML element, the Native render 		mode will have the same effect as the Classic one. 	
	 		The default render mode of the control is Classic and you have 		the option to either explicitly set it to Lightweight or leverage 		the Auto mode to have the control choose the best rendering based 		on the user's browser. 	
	
		Note: In order to provide optimal experience for your end users, 		we recommend that you use only one type of render mode for a control on a given 			page. For example, if you have two instances of RadFormDecorator on the page, 		it will be best if both of them use the same render mode. 	
	
        Note: The Material skin is available only for the modern Lightweight render mode.
        Change the skin or the mode to properly visualize the demonstrated control.
    
    
		Notes on the statistics:
* - The markup is obtained through the dev toolbar of the browser, 		because the additions from RadFormDecorator are created with JavaScript. The HTML 		that is measured is just the contents of the div with the sample on the left (fieldsets, 		dropdowns, textboxes, etc.). The HTML size in the table reflects the change in this 		div's contents for the given page, compared with the same div when RadFormDecorator is not used. 		It may vary with different elements and their size.
** - The image sprites that are loaded are larger in size with 		Lightweight RenderMode, but they also contain a common sprite that holds elements 		used by many controls in the suite (e.g., arrows, buttons) and is only needed once. 		With more controls on the page the benefit is on the side of the Lightweight RenderMode 		because this resource will be loaded only once. Also, the Classic RenderMode has 		a larger number of image sprites which means more requests.