Sync with Kendo UI Professional

Author: kendo-bot

docs-aspnet/backwards-compatibility/2025-backwards-compatibility.md

@@ -51,6 +51,11 @@ The [`IconClass()`](/api/kendo.mvc.ui.fluent/popoveractionbuilder#iconclasssyste
         </actions>
     </kendo-popover>
 ```
+
+### Pager Position in Grid TagHelper
+
+The [`position`](/api/kendo.mvc.taghelpers/gridpageablesettingstaghelper#attributes) attribute of the Grid TagHelper `pageable` configuration accepts a `PagerPosition` enum type instead of the previously used `GridPagerPosition`.
+
 {% else %}
 
 ### Kendo.Mvc.Export
@@ -73,6 +78,17 @@ As of the Q2 2025 release, the following NuGet packages and assemblies no longer
 
 The `Telerik.Zip` library will continue to be shipped as a standalone library.
 
+### Pager
+
+The [responsive behavior]({% slug responsive_pager_aspnet%}) of the Pager has been enhanced, which introduces the following changes:
+
+* The Pager's sizing is no longer based on breakpoints. Instead, the optimized responsive behavior renders as many elements as possible within the available space.
+* `Input` Type&mdash;When the [`Input()`](/api/kendo.mvc.ui.fluent/pagerbuilder#inputsystemboolean) option of the Pager is enabled, the TextBox next to the navigation arrows is replaced with a NumericTextBox, and the numeric page number buttons are no longer rendered.
+* Page Selection&mdash;The page selection drop-down has been replaced with a NumericTextBox for improved user interaction.
+* `NumbersSelectLabel()` Property&mdash;The [`NumbersSelectLabel()`](/api/kendo.mvc.ui.fluent/pagermessagessettingsbuilder#numbersselectlabelsystemstring) option in the `Messages()` configuration has been removed as it is no longer needed with the replacement of the page selection drop-down.
+
+> These changes to the Pager affect all components that use a built-in pager, including the Grid, PDFViewer, and other data management components.
+
 ## {{ site.product }} Q1 2025
 
 ### License Activation

docs-aspnet/html-helpers/data-management/pager/adaptive-mode.md

@@ -0,0 +1,33 @@
+---
+title: Adaptive Mode
+page_title: Adaptive Mode
+description: "Learn how to configure the adaptive behavior of the the Telerik UI Pager component for {{ site.framework }}."
+slug: htmlhelpers_pager_adaptive_mode
+position: 4
+---
+
+# Adaptive Mode
+
+The Telerik UI for {{ site.framework }} Pager supports an adaptive mode that provides a mobile-friendly rendering of its [built-in drop-down that allows the user to change the page size]({% slug settings_pager_aspnet%}#settings).
+
+To enable the adaptive rendering mode, set the `AdaptiveMode()` property to `AdaptiveMode.Auto`.
+
+The Pager component automatically adapts to the current screen size and changes the rendering of the drop-down for page size selection accordingly. On medium-sized screens, the options list is displayed as docked to the bottom of the screen, while on smaller screens, it is rendered as a full-screen modal dialog. In all other scenarios, including when the `AdaptiveMode()` option is not specified or is set to its default value of `AdaptiveMode.None`, the standard popup is rendered docked to the input of the drop-down.
+
+The adaptive mode changes the rendering of the Pager's drop-down element based on the screen resolution of the device (the horizontal value in `px`) with the following breakpoints:
+
+* Small screens—up to 500 px.
+* Medium screens—between 501 px and 768 px.
+* Large screens—over 768 px.
+
+The following example demonstrates how to enable the adaptive mode of the Pager by using the `AdaptiveMode()` option.
+
+<demo metaUrl="pager/adaptive_mode/" height="600"></demo>
+
+## See Also
+
+* [Adaptive Rendering of the Components]({% slug adaptive_rendering%})
+* [Server-Side API of the Pager HtmlHelper](/api/pager)
+{% if site.core %}
+* [Server-Side API of the Pager TagHelper](/api/taghelpers/pager)
+{% endif %}

docs-aspnet/html-helpers/data-management/pager/events.md

@@ -3,7 +3,7 @@ title: Events
 page_title: Events
 description: "Learn how to handle the events of the Telerik UI Pager component for {{ site.framework }}."
 slug: pager_events
-position: 5
+position: 6
 ---
 
 # Events

docs-aspnet/html-helpers/data-management/pager/overview.md

@@ -111,12 +111,12 @@ The following example demonstrates how to tie a pager to a data source and enabl
 
 ## Functionality and Features
 
-* [Pager Settings and Types]({% slug settings_pager_aspnet %})—You can choose between the available settings and types.
-* [Responsive Pager]({% slug responsive_pager_aspnet  %})—The Pager supports responsive design by default. 
-* [Pager Templates]({% slug templates_pager_aspnet %})—Customize the look and feel of the Pager with Kendo Templates.
-* [Globalization and Messages]({% slug globalization_pager_aspnet %})—The globalization process combines the translation of component messages (localization) with adapting them to specific cultures (internationalization and right-to-left support).
-* [Accessibility]({% slug htmlhelpers_pager_accessibility %})—The Pager is accessible by screen readers and provides WAI-ARIA, Section 508, WCAG 2.2, and keyboard support.
-
+* [Pager Settings and Types]({% slug settings_pager_aspnet %})—Control the Pager functions and rendering.
+* [Responsiveness]({% slug responsive_pager_aspnet %})—The Pager supports responsive design by default. 
+* [Adaptive Mode]({% slug htmlhelpers_pager_adaptive_mode %})—Enable the adaptive mode that changes the rendering of the Pager based on the screen resolution of the device.
+* [Templates]({% slug templates_pager_aspnet %})—Customize the look and feel of the Pager.
+* [Globalization]({% slug globalization_pager_aspnet %})—Localize the texts and tooltips of the Pager.
+* [Accessibility]({% slug htmlhelpers_pager_accessibility %})—The Pager is accessible by screen readers and provides WAI-ARIA, Section 508, WCAG 2.2, and keyboard support.
 
 ## Next Steps
 

docs-aspnet/html-helpers/data-management/pager/responsive.md

@@ -1,45 +1,37 @@
 ---
-title: Responsive Pager
+title: Responsiveness
 page_title: Responsive Telerik UI Pager component for {{ site.framework }}
 description: "Get started with the Pager component for {{ site.framework }} and learn about its responsive feature."
 slug: responsive_pager_aspnet
-position: 4
+position: 3
 ---
 
-# Responsive Design
+# Responsiveness
 
-The Pager component for {{ site.framework }} is responsive by default. To disable the responsive behavior and have all of its elements visible at all times use the `Responsive()` method and pass `false` as a parameter.
+The Pager component is responsive by default. 
 
-## Visible Elements
+To disable the responsive behavior, set the [`Responsive()`](/api/kendo.mvc.ui.fluent/pagerbuilder#responsivesystemboolean) option to `false`. As a result, all Pager elements are visible, no matter the screen resolution of the device.
 
-The Pager widget determines which internal elements to render based on its width. When the Pager width is greater than or equal to 600 pixels, all elements are visible:
+> Starting with version Q2 2025, the Pager's sizing is no longer based on fixed breakpoints. Instead, the optimized responsive behavior renders as many elements as possible within the available space. For more information, refer to the [Breaking Changes section]({% slug breakingchanges_2025%}#pager).
 
-- `Page Sizes Dropdown`
-- `Numeric Page Number Buttons` or a `Numeric Input` if the pager is an `Input` one.
-- `Info element`
+The responsive Pager determines which elements to render based on the available space. The component's elements are displayed in the following order:
 
-## Breaking Points
+* [Numeric Page Number Buttons](/api/kendo.mvc.ui.fluent/pagerbuilder#numericsystemboolean) or a [Numeric Input](/api/kendo.mvc.ui.fluent/pagerbuilder#numericsystemboolean), if the Pager type is set to `Input()`.
+* [Page Sizes Dropdown](/api/kendo.mvc.ui.fluent/pagerbuilder#pagesizessystemboolean)
+* [Info label](/api/kendo.mvc.ui.fluent/pagerbuilder#infosystemboolean)
+* [Refresh button](/api/kendo.mvc.ui.fluent/pagerbuilder#refreshsystemboolean) (if enabled)
 
-When the Pager width is greater than or equal to 600 pixels, all elements are visible:
+As the screen size decreases, the elements are hidden from the bottom to the top of this list, starting with the `Refresh` button, to maintain optimal layout within the available space.
 
-![{{ site.product_short }} A Pager widget at over 600px resolution](../../../images/pager-responsive/pager-width-over-600.png)
+On smaller screens, when using the default [`Numeric()`](/api/kendo.mvc.ui.fluent/pagerbuilder#numericsystemboolean) Pager type, the numeric page buttons are automatically replaced with a single input field that functions the same way as when the [`Input()`](/api/kendo.mvc.ui.fluent/pagerbuilder#numericsystemboolean) option is enabled.
 
-When the Pager width is greater than 480 and less than 600 pixels, the label showing the current paging information is hidden:
-
-![{{ site.product_short }} A Pager widget between 480 and 600px resolution](../../../images/pager-responsive/pager-width-480-600.png)
-
-When the Pager width is greater than 360 and less than 480 pixels, the current page is represented by a native `<select/>` element. The `pageSizes` dropdown and the label showing the current paging information are hidden.
-
-![{{ site.product_short }} A Pager widget between 360 and 480px resolution](../../../images/pager-responsive/pager-width-360-480.png)
-
-When the Pager width is less than 360 pixels, the current page is represented by a native `<select/>` element. The `pageSizes` dropdown and the label showing the current paging information are hidden.
+## See Also
 
-![{{ site.product_short }} A Pager widget under 360 pixels](../../../images/pager-responsive/pager-width-under-360.png)
+* [Use the Pager in Adaptive Mode]({% slug htmlhelpers_pager_adaptive_mode %})
+* [Server-Side API of the Pager HtmlHelper](/api/pager)
+{% if site.core %}
+* [Server-Side API of the Pager TagHelper](/api/taghelpers/pager)
+{% endif %}
+* [Client-Side API  of the Pager](https://docs.telerik.com/kendo-ui/api/javascript/ui/pager)
 
-## See Also
 
-* [Pager Client-Side API](https://docs.telerik.com/kendo-ui/api/javascript/ui/pager)
-* [Pager Server-Side API](/api/pager)
-* [Pager Settings and Types]({% slug settings_pager_aspnet %})
-* [Pager Templates]({% slug templates_pager_aspnet %})
-* [Globalization and Messages]({% slug globalization_pager_aspnet %})

docs-aspnet/html-helpers/data-management/pager/templates.md

@@ -1,12 +1,12 @@
 ---
-title: Pager Templates
+title: Templates
 page_title: Pager Templates
 description: "Get started with the {{ site.framework }} Pager and learn about its templating options."
 slug: templates_pager_aspnet
-position: 3
+position: 5
 ---
 
-# Pager Templates
+# Templates
 
 The {{ site.framework }} Pager component features templates for its page number links.
 

docs-aspnet/html-helpers/editors/autocomplete/adaptive-mode.md

@@ -16,6 +16,8 @@ Adaptiveness is an advanced capability that enhances the Telerik UI for {{ site.
 
 The AutoComplete supports an adaptive mode that provides a mobile-friendly rendering of its popup. To enable the adaptive rendering mode, set the [`AdaptiveMode()`](/api/kendo.mvc.ui.fluent/autocompletebuilder#adaptivemodekendomvcuiadaptivemode) property to `AdaptiveMode.Auto`.
 
+> Starting with the 2025 Q2 release, when the adaptive rendering mode is enabled and the component is accessed on a mobile device, the popup will open as soon as the component receives focus. In previous versions, the popup only opened once the user began typing.
+
 The AutoComplete component automatically adapts to the current screen size and changes its rendering accordingly. On medium-sized screens, the suggestion list is displayed as docked to the bottom of the screen, while on smaller screens, it is rendered as a full-screen modal dialog. In all other scenarios, including when the `AdaptiveMode()` option is not specified or is set to its default value of `AdaptiveMode.None`, the standard popup is rendered docked to the input of the component.
 
 The adaptive mode changes the rendering of the AutoComplete popup element based on the screen resolution of the device (the horizontal value in `px`) with the following breakpoints:

docs-aspnet/html-helpers/editors/colorpicker/adaptive-mode.md

@@ -10,6 +10,8 @@ position: 7
 
 The Telerik UI for {{ site.framework }} ColorPicker supports an adaptive mode that renders a mobile-friendly popup. To enable the adaptive rendering mode, set the `AdaptiveMode()` property to `AdaptiveMode.Auto`.
 
+> Starting with the 2025 Q2 release, when the adaptive rendering mode is enabled and the component is accessed on a mobile device, the popup will open as soon as the component receives focus. In previous versions, the popup only opened once the user began typing.
+
 The ColorPicker component automatically adapts to the current screen size and changes its rendering accordingly. On medium-sized screens, the suggestion list is displayed as docked to the bottom of the screen, while on smaller screens, it is rendered as a full-screen modal dialog. In all other scenarios, including when the `AdaptiveMode()` option is not specified or is set to its default value of `AdaptiveMode.None`, the standard popup is rendered docked to the input of the component.
 The adaptive mode changes the rendering of the ColorPicker popup element based on the screen resolution of the device (the horizontal value in `px`) with the following breakpoints:
 

docs-aspnet/html-helpers/editors/combobox/adaptive-mode.md

@@ -14,6 +14,8 @@ Adaptiveness is an advanced capability that enhances the Telerik UI for {{ site.
 
 The ComboBox supports an adaptive mode that provides a mobile-friendly rendering of its popup. To enable the adaptive rendering mode, set the [`AdaptiveMode()`](/api/kendo.mvc.ui.fluent/comboboxbuilder#adaptivemodekendomvcuiadaptivemode) property to `AdaptiveMode.Auto`.
 
+> Starting with the 2025 Q2 release, when the adaptive rendering mode is enabled and the component is accessed on a mobile device, the popup will open as soon as the component receives focus. In previous versions, the popup only opened once the user began typing.
+
 The ComboBox component automatically adapts to the current screen size and changes its rendering accordingly. On medium-sized screens, the suggestion list is displayed as docked to the bottom of the screen, while on smaller screens, it is rendered as a full-screen modal dialog. In all other scenarios, including when the `AdaptiveMode()` option is not specified or is set to its default value of `AdaptiveMode.None`, the standard popup is rendered docked to the input of the component.
 
 The adaptive mode changes the rendering of the ComboBox popup element based on the screen resolution of the device (the horizontal value in `px`) with the following breakpoints:

docs-aspnet/html-helpers/editors/datepicker/adaptive-mode.md

@@ -14,6 +14,8 @@ Adaptiveness is an advanced capability that enhances the Telerik UI for {{ site.
 
 The DatePicker supports an adaptive mode that provides a mobile-friendly rendering of its calendar popup. To enable the adaptive rendering mode, set the [`AdaptiveMode()`](/api/kendo.mvc.ui.fluent/datepickerbuilder#adaptivemodekendomvcuiadaptivemode) property to `AdaptiveMode.Auto`.
 
+> Starting with the 2025 Q2 release, when the adaptive rendering mode is enabled and the component is accessed on a mobile device, the popup will open as soon as the component receives focus. In previous versions, the popup only opened once the user began typing.
+
 The DatePicker component automatically adapts to the current screen size and changes its rendering accordingly. On medium-sized screens, the calendar is displayed as docked to the bottom of the screen, while on smaller screens, it is rendered as a full-screen modal dialog. In all other scenarios, including when the `AdaptiveMode()` option is not specified or is set to its default value of `AdaptiveMode.None`, the standard calendar popup is rendered docked to the input of the component.
 
 The adaptive mode changes the rendering of the DatePicker popup element based on the screen resolution of the device (the horizontal value in `px`) with the following breakpoints: