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: _templates/button/distorted-appearance.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,7 +1,7 @@
1
1
#intro
2
2
This help article describes what to do when you have an appearance issue with **@{control}** and provides a resolution.
3
3
4
-
The appearance of **@{control}** may be distorted (**Figure 1**) when the control is declarted on the same page that contains a **RadButton** with a `Classic``RenderMode` (*i.e., the default `RenderMode`*).
4
+
The appearance of **@{control}** may be distorted (**Figure 1**) when the control is declared on the same page that contains a **RadButton** with a `Classic``RenderMode` (*i.e., the default `RenderMode`*).
5
5
6
6
>caption Figure 1: Distorted appearance of **@{control}** when placed on the same page with **RadButton**`RenderMode`="`Classic`".
Copy file name to clipboardExpand all lines: controls/numerictextbox/features/validation.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -20,13 +20,13 @@ The **RadInput** controls support ASP.NET validators (both client and server sid
20
20
>
21
21
22
22
23
-
To use ASP.NET validators with **RadInput** controls, simply set the ID of the **RadInput** control as the value of the **ControlToValidate** property of the validator.
23
+
To use ASP.NET validators with **RadInput** controls set the ID of the **RadInput** control as the value of the **ControlToValidate** property of the validator.
24
24
25
25
Since Q2 2012 there are some modifications for RadInput validation.The main idea is to render only the input element all the time, and remove the span element and the excessive inputs. To be achieved this the validation value is stored in [“expando”](https://msdn.microsoft.com/en-us/library/89t1khd2%28v=vs.94%29.aspx) property and we submit real value through the client state. Also, the [ValidatorGetValue](https://msdn.microsoft.com/en-us/library/aa338815%28v=vs.71%29.aspx) function of the [asp:Validators](https://msdn.microsoft.com/en-us/library/debza5t0.aspx) was overriden to look our expando property called “RadInputValidationValue”.
26
26
27
27
## Example
28
28
29
-

29
+

30
30
31
31
The following declaration shows the use of a required field validator from the form above:
32
32
@@ -63,7 +63,7 @@ The validator controls have a **ValidationGroup** property. The **RadInput** con
63
63
64
64
## Display ErrorMessage inside RadInput
65
65
66
-
The following example demonstrates how you could display your ErrorMessage inside the input itself following an unsuccessful validation.
66
+
The following example demonstrates how you can display your ErrorMessage inside the input itself following an unsuccessful validation.
Copy file name to clipboardExpand all lines: controls/toolbar/getting-started/overview.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -56,7 +56,7 @@ This tutorial will walk you through creating a **RadToolBar** and shows how to:
56
56
57
57
1. Select the "Details" button again and click the **Add RadToolBarButton to drop-down** button two more times to add two more buttons to the drop-down list.
58
58
59
-
* On the first of these (the second button in the drop-down list), set the **IsSeparator** property to **True** and the **Text** property to an empty string.The item builder should now look like the following:()
59
+
* On the first of these (the second button in the drop-down list), set the **IsSeparator** property to **True** and the **Text** property to an empty string.The item builder should now look like the following:()
60
60
61
61
1. Click the **Add RadToolBarSplitButton** button () to add a split button to the toolbar.
Copy file name to clipboardExpand all lines: controls/window/troubleshooting/executing-javascript-code-from-server.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,13 +12,13 @@ position: 4
12
12
13
13
14
14
15
-
This is a pretty common scenario when working with WebForms. There are many ways to achieve the desired result, but they have one thing in common – you should make sure that the controls are fully loaded in the page before trying to get a reference to them and use them in your JavaScript code.
15
+
This is a common scenario when working with WebForms. There are many ways to achieve the desired result, but they have one thing in common – you should make sure that the controls are fully loaded in the page before trying to get a reference to them and use them in your JavaScript code.
16
16
17
17
>note You can check the [Executing JavaScript Code from Server-side in Web Forms and ASP.NET AJAX](https://www.telerik.com/support/kb/aspnet-ajax/details/executing-javascript-code-from-server-side-in-web-forms-and-asp.net-ajax) KB article for more abstract code snippets.
18
18
> Before you dive and test the different solutions make sure that:
19
19
> * The code is actually inserted on the page – the easiest way is to put a simple alert() and check if it is fired.
20
20
> * The controls are rendered on the page before referencing them in your JavaScript function
21
-
> * If you are manually inserting the '<script>' tags – that you have set either the type (type='text/javascript') or the language (language='javascript') attributes
21
+
> * If you are manually inserting the `<script>` tags – that you have set either the type (`type='text/javascript'`) or the language (`language='javascript'`) attributes
22
22
23
23
## The simplest way
24
24
@@ -208,4 +208,4 @@ Calling a JavaScript function from the server is a relatively easy task. Just ma
208
208
209
209
1. The controls are rendered on the page before referencing them in your JavaScript function
210
210
211
-
1. If you are manually inserting the <script> tags – that you have set either the type (type='text/javascript') or the language (language='javascript') attributes.
211
+
1. If you are manually inserting the `<script>` tags – that you have set either the type (type='text/javascript') or the language (language='javascript') attributes.
Copy file name to clipboardExpand all lines: integration/jquery/jquery-intellisense.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -30,9 +30,9 @@ Separate sections below explain the cases for the different Visual Studio versio
30
30
31
31
Visual Studio 2017 uses a new Intellisense mode for JavaScript based on TypeScript. You can revert to the old behavior by going to **Tools** > **Options** > **Text Editor** > **JavaScript/TypeScript** > **Language Service** and **uncheck** the checkbox from **Enable the new JavaScript Language service**. Make sure to restart Visual Studio for the changes to take effect.
32
32
33
-

33
+

34
34
35
-
With this, you can use the old JavaScript documenttion like in [Visual Studio 2012 and Visual Studio 2013 with Q3 2012 or later](#jquery-intellisense-in-vs-2012-and-vs-2013-using-telerik-ui-for-aspnet-ajax-q3-2012-or-later).
35
+
With this, you can use the old JavaScript documentation like in [Visual Studio 2012 and Visual Studio 2013 with Q3 2012 or later](#jquery-intellisense-in-vs-2012-and-vs-2013-using-telerik-ui-for-aspnet-ajax-q3-2012-or-later).
36
36
37
37
````ASP.NET
38
38
<!-- This can enable the old JS intellisense for the current page -->
Copy file name to clipboardExpand all lines: integration/visual-studio/how-to-use-javascript-intellisense-for-the-telerik-controls.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -139,9 +139,9 @@ function OnClientClicking(sender, args) {
139
139
140
140
Visual Studio 2017 uses a new Intellisense mode for JavaScript based on TypeScript. You can revert to the old behavior by going to **Tools** > **Options** > **Text Editor** > **JavaScript/TypeScript** > **Language Service** and **uncheck** the checkbox from **Enable the new JavaScript Language service**. Make sure to restart Visual Studio for the changes to take effect.
141
141
142
-

142
+

143
143
144
-
With this, you can use the old JavaScript documenttion provided in the `vsdoc` files.
144
+
With this, you can use the old JavaScript documentation provided in the `vsdoc` files.
145
145
146
146
````ASP.NET
147
147
<!-- This can enable the old JS intellisense for the current page -->
Copy file name to clipboardExpand all lines: styling/controlling-visual-appearance/controlling-absolute-positioning-with-z-index.md
+8-8Lines changed: 8 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -13,7 +13,7 @@ position: 8
13
13
14
14
15
15
16
-
A number of Telerik controls render with absolute positioning and have their default z-indexes as shown below:
16
+
Many Telerik controls render with absolute positioning and have their default z-indexes as shown below:
17
17
18
18
19
19
@@ -73,7 +73,7 @@ A number of Telerik controls render with absolute positioning and have their def
73
73
74
74
75
75
76
-
In different scenarios, you may need to change these values in order to ensure that one specific control will be shown above the other—for example **RadWindow** over **RadMenu**. To do this, you can simply set the value of the z-index property of every control by using the common style property, e.g.:
76
+
In different scenarios, you may need to change these values to ensure that one specific control will be shown above the other—for example **RadWindow** over **RadMenu**. To do this, you can set the value of the z-index property of every control by using the common style property, e.g.:
0 commit comments