This demo showcases the two different rendering modes of Telerik's ASP.NET Dock control: Classic and Lightweight.
-
Classic rendering is the long-standing rendering mode of the control in which its layout is implemented using table elements.
-
Lightweight rendering leverages HTM5 and CSS3 to deliver semantic HTML to the browser, but the control may lose its rounded corners, gradients and shadows in non-modern browsers. With this rendering, some 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 RadDock 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 RadDock 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 size is calculated automatically in the code-behind by rendering a simple RadDock instance on a blank page.
* - The larger size of the sprite is due to the common spite RadDock uses for its buttons and arrows. A lot of Telerik controls use this sprite, so with more complex pages it will be loaded only once, which will, ultimately, make it more efficient. The Classic RenderMode also performs several requests for image sprites, even if they are smaller in size.