Bug report

Regression
Pager incorrectly displays DDL when responsive is disabled with the latest service pack 2023.2.829

Reproduction of the problem
Dojo https://dojo.telerik.com/EJUBiHaW

Expected/desired behavior
When responsiveness is disabled Pager shall look as its older design - https://www.figma.com/file/gWUIux95BHxemqWwOw9ZwB/Default-Theme---Internal-Usage?type=design&node-id=4708%3A103019&mode=design&t=udeyWyYFUsbBpUl7-1

Environment
Kendo UI version: [2023.2.829]
Browser: [all]

The pager feature is a nice addition, but it could be enhanced with the following additional options which would help if there are a lot of pages to scroll through:

• Add an option to move to the next/prior set of pages.  For example, if 10 pages are showing and you are on page 1 it would jump to page 11, page 12 would jump to 22 (and display pages 11 - 20), and so on, or if going backwards 39 would jump to 29 (and display pages 20 - 30), and so on.
• It would be nice to enter a specific page number to jump to and hit Apply or OK to go directly to that page so you don't have to jump through numerous pages you don't care about (especially when there are hundreds or thousands of pages based on the current number of rows showing).  So if I wanted to jump to page 654 pages 651 - 650 would be displayed with 654 selected).
• It would also be nice if there was a way to display the total number of pages (to make the page jump more manageable).  This would require making a call to determine the total number of pages based on the rows in the database and number of rows displayed per page or otherwise updating the value - and not displaying a total if the value returned was null.

The Pager keyboard navigation now includes the keys ENTER and ESC that allow to "enter" a detailed pager navigation as explained in https://docs.telerik.com/kendo-ui/controls/data-management/pager/accessibility/keyboard-navigation.

However, the key events bubble up the DOM. In our case, this causes unwanted effects like closing popups etc. (we close popups on ESC).

Shouldn't the propagation be prevented for keyboard events that are handled by the pager itself?

I've created a small DOJO which demostrates this behavior: Note how the keydown event of the outer container is always fired, even if ESC was pressed to navigate inside the pager.