This behavior can be observed with the example below.

https://demos.telerik.com/aspnet-ajax/listview/examples/paging/pagingwithraddatapager/defaultcs.aspx

Enter a value for Page and click the Go button. Either the page will be updated to the expected page or the pager will fail to change the page. Clicking Go again usually seems to work if it failed. It may take a several tries to observe this behavior as it happens inconsistently.

If one wants to change the current page index one should provide a value for the CurrentPageIndex property. Example RadDataPager1.CurrentPageIndex=5;

I would just like to be able to easily control the horizontal alignment of the paging buttons of a RadDataPager control. I should be able to set the paging buttons left, center, or right and when I choose that the entire set of buttons follows that command.

Right now they align to the left so the only option is to do some margin stuff in CSS to move them around. While this sort of works it's not very good, especially when the number of page button changes (based on search results). Also, this method is terrible on mobile phones with different widths.

I opened Support ID 873213 on this and they suggested I post it as a feature request here. Seems like this option is a no brainer to add.

Similar to the rdpNumPart class on RadDataPagerButtonField, the addition of a default class to the template field would allow for easier targeting of this area while custom skinning the DataPager. On a large scale, it's much cleaner than adding your own wrapper divs within the template field.

Improve ClientSide events of RadDataPager to work with server side binding on user action. Currently the work only when performing operations using the API of the pager's object.

I would like more control over the data pagers rendered page numbers.

It's very simple thing I need... 
http://<currenturlwithlistview>/page/<number>

...this isn't a route handled by MVC\ASP or anything where I can give it an SEO name or route name or whatever.  It's a sitefinity route which uses another mechanism the datapager doesn't understand.

AND THAT'S FINE! :)  ...just give me the ability to define the route "path" I guess like even something as simple as a String.Format..."RouteFormat" property or something

RouteFormat="/page/{0}"

Steve