pagingOptions.currentPage doesn't get set properly with Angular >1.1.1.

[dnordberg]

Using Ng-grid 2.0.7 pagingOptions.currentPage doesn't get set properly with Angular >=1.1.3 (The version provided by ng-grid in the lib folder).

It does work when reverting back to 1.0.2 which is the version defined in the plnkr provided on the ng-grid documentation page. The regression seems to have been introduced in 1.1.3 (1.1.1 works fine).

An example that illustrates the issue:
http://plnkr.co/edit/jxdukO?p=preview

The input field used to display the current page shows no initial value, using the paging buttons does not change the value as expected even after inputing a value manually. Also the validation doesn't seem to work as the input gets marked as invalid for valid numbers.

[chiefy]

👍

Also happens w/ ng-grid 2.0.7 w/ ng 1.2.0rc1 😨

This appears to be some kind of data-binding issue with the type="number" and ng parsing it as a string? I changed the template to use input="text" and everything seems to work.

[giosakti]

+1
also having this issue on 1.1.5, perhaps related is the fact that I can click next up to page 3, even though the number of pages is only 2

[geoffreytran]

+1
Having this issue on 1.2

[tbertenshaw]

Also experiencing this issue with 1.2.0rc1, easily replicatable by changing the angular version referenced in the serverside paging plunkr http://plnkr.co/edit/50vJrs?p=preview

[chiefy]

Just spent some time looking into this - for an easy fix just remove the max attribute from the number input and it works, although it obviously won't restrict the user navigating past pages with content (though it won't break the UI and they can easily page back).

[geoffreytran]

My solution was to change the input type to text from number as validation for number doesn't appear to work properly.

On Sep 3, 2013, at 10:58 AM, Christopher Najewicz notifications@github.com wrote:

Just spent some time looking into this - for an easy fix just remove the max attribute from the number input and it works, although it obviously won't restrict the user navigating past pages with content (though it won't break the UI and they can easily page back).

—
Reply to this email directly or view it on GitHub.

[chiefy]

@geoffreytran yeah, the max validation wasn't working properly, my PR fixes the issue. 🍔

[roblarsen]

fixed with above PR

[vijender1256]

$scope.yourGridOptions.paginationCurrentPage = 1; --> will reset the pagenumber of angular ui-grid :)

[sudhirgoswami]

https://stackoverflow.com/questions/45453359/how-to-get-page-number-in-slickgrid-while-click-the-page-numbers.

Please help on this..