`<b-pagination>` Should not go to the first page when page numbers change

I found the code in paginator.js watch: { numberOfPages(newVal) { if (newVal === this.localNumPages) { /* istanbul ignore next */ return } this.localNumPages = newVal this.currentPage = 1 } },

Why you change currentPage to 1 when the numberOfPages is changed ?

Our use case is: delete all of data in current page, then I go to last page and fetch data again. The currentPage should keep the same as value model.

[luchomatic]

@luchomatic which version are you using of BootstrapVue? b-pagination-nav will adjust the selected page number based on the current route or page URL. b-pagination will change to the first page under certain circumstances (i.e. the current page is greater than the number of pages, etc)

I was able to fix it, my problem was that I loaded the elements to paginate using ajax.

So when my content loaded, it would trigger a pagination pagesCount change, and then it will move the pointer to the first page. (which was my problem and the subject of this thread).

So to solve it I added a “v-if” condition on the paginator to only load it when the content to paginate is already there.

[stefandesu]

One problem with this is that even when you keep your internal data structure on the correct page, the display of the pagination switches to page 1. What we were doing is to “deny” the page change (by using the @change event only and ignoring the @input event), but even though the data for the correct page was shown, the pagination displayed page 1. The only workaround I could find was to change the page to page 1 and on the next tick, change it back to the previous page so that b-pagination would reevaluate and show the correct page again.

Is there maybe a better way around this?

Edit: I think an option to control this behavior would be best, i.e. some way to deactivate the automatic page change.