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

b:datatable per-column filtering returns no rows if current page # was greater than filter result has #462

Closed
susanne69 opened this issue Jul 11, 2016 · 3 comments
Assignees
Labels
Solved This ticket has been solved. If it's still open, we're waiting for the user's confirmation.
Milestone

Comments

@susanne69
Copy link

susanne69 commented Jul 11, 2016

Hello again,
I have moved to 0.9.0.
The per-column filtering in b:datatable returns no rows if current page # was greater than result has.

Imagine 3 rows and 1 row per page. The column has values A,B and C.
I am on page #1 and filter for 'C' filter shows correctly one row with C.
The filter is removed again and I move to page 3.
I am filtering again for 'C' and no row is returned. Only if I click on page #1 the lost row shows up from the dark. Poor row.

Kind regards,
Susanne

@susanne69 susanne69 changed the title b:datatable per-column filtering returns no values if current page # was greater than filter result has b:datatable per-column filtering returns no rows if current page # was greater than filter result has Jul 11, 2016
@stephanrauh
Copy link
Collaborator

I'm not sure if we can solve this bug. It seems to be a bug of the underlying JavaScript widget (https://datatables.net/). But of course I'd like to have a look myself before reporting a bug on their bugtracker.

@stephanrauh
Copy link
Collaborator

BTW, you may want to move to 0.9.1. It's not a big update - basically compatibility to Java 6/7 and a few minor bugfixes.

@TheCoder4eu TheCoder4eu added this to the v1.5.0 milestone Apr 17, 2017
@stephanrauh
Copy link
Collaborator

Good news: I've just tried to reproduce the bug. It's gone away. I suppose the datatables.net team has noticed the bug themselves.

@stephanrauh stephanrauh self-assigned this Aug 3, 2019
@stephanrauh stephanrauh added the Solved This ticket has been solved. If it's still open, we're waiting for the user's confirmation. label Aug 3, 2019
@TheCoder4eu TheCoder4eu modified the milestones: v1.5.0, v1.4.2 Aug 28, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Solved This ticket has been solved. If it's still open, we're waiting for the user's confirmation.
Projects
None yet
Development

No branches or pull requests

3 participants