Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Reset to first page after filtering #143

Closed
bozjator opened this issue Mar 24, 2016 · 2 comments
Closed

Reset to first page after filtering #143

bozjator opened this issue Mar 24, 2016 · 2 comments
Assignees
Labels
Type: Enhancement Issue contains an enhancement related to a specific component. Additional functionality has been add
Milestone

Comments

@bozjator
Copy link

When positioned on non-first page in data table and changing one of the filters, a lazy load method metadata first field is set to e.g. 3. I think it should be set to 0, since it will return entirely new set of data from server (e.g. after filtering I had results for less then one page but they weren't shown since first page was skipped).
In case when lazy load method is called due to filter change, first field should be set to zero.

BR, Blaž

@cagataycivici
Copy link
Member

Could you please clarify what do you mean by skip metadata field?

@bozjator bozjator changed the title Data table: skip metadata field is incorrect when filtering with lazy load. Data table: metadata field "first" is incorrect when filtering with lazy load. Apr 2, 2016
@bozjator
Copy link
Author

bozjator commented Apr 2, 2016

I'm sorry, i meant metadata field event.first.

@cagataycivici cagataycivici added the Type: Enhancement Issue contains an enhancement related to a specific component. Additional functionality has been add label Apr 9, 2016
@cagataycivici cagataycivici added this to the 1.0.0-beta.1 milestone Apr 9, 2016
@cagataycivici cagataycivici self-assigned this Apr 9, 2016
@cagataycivici cagataycivici changed the title Data table: metadata field "first" is incorrect when filtering with lazy load. Reset to first page after filtering Apr 9, 2016
atretyak1985 pushed a commit to Nanitor/primeng that referenced this issue Jul 18, 2020
Nanitor Admin UI - Adding benchmarks - Font too big primefaces#141
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type: Enhancement Issue contains an enhancement related to a specific component. Additional functionality has been add
Projects
None yet
Development

No branches or pull requests

2 participants