You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: common-features/dimensions.md
+60Lines changed: 60 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -20,3 +20,63 @@ For elements with **special positioning** (`Top` and `Left` properties), keep in
20
20
21
21
When setting **percentage values** (such as `100%` or `50%`), keep in mind the following - according to the web standards, elements which have their height set in percentage require that the height of their parent is also explicitly set. This requirement applies recursively until either an element with a pixel height or the html element is reached. Elements that are 100% high should not have margins, paddings, borders, or sibling elements.
22
22
23
+
## Examples
24
+
25
+
The examples here showcase different units and examples of using them to set dimensions and positions. The results you get may vary from the screenshots here because of different CSS rules in your project and different browser/screen sizes. Review the explanations in the code for more details on what to expect.
26
+
27
+
>caption Setting sizes in different dimensions (percent, pixel, vw in this sample)
The parent element of the window is the TelerikRootComponent which should match the app element and the viewport.
71
+
<br />
72
+
This window will be 100px off the top left corner of the viewport in a blank app without special CSS rules. You can also use other units, such as percent.
73
+
<br />
74
+
Also, the size of this window will depend on the viewport size - resize your browser to see the effects.
75
+
</WindowContent>
76
+
<WindowTitle>Examples of offsets and dimensions</WindowTitle>
0 commit comments