You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When we try to use the filter when we don't have row or result this one is unusable.
This example is on your documentation in 'filter row' section with the filter 'agent'
[primefaces.org/primeng-v13-lts/#/table/filter](https://www.primefaces.org/primeng-v13-lts/#/table/filter
1 go to https://www.primefaces.org/primeng-v13-lts/#/table/filter
2 go to the section 'Filter Row'
3 filter with 'Xuxue Feng' agent and use 'Ukraine' in country.
4 Try to change filter agent --> It's impossible to see and use the filter
Expected behavior
No response
The text was updated successfully, but these errors were encountered:
The issue you mentioned seems to appear in an outdated version of ours. Between the version you referred to and our current version (v17x), we've made numerous improvements, bug fixes, and enhancements, so the issue might have been addressed. If you encounter it in the current version as well, please open an issue with a Stackblitz example.
Describe the bug
When we try to use the filter when we don't have row or result this one is unusable.
This example is on your documentation in 'filter row' section with the filter 'agent'
[primefaces.org/primeng-v13-lts/#/table/filter](https://www.primefaces.org/primeng-v13-lts/#/table/filter
Environment
documentation on your website
Reproducer
https://www.primefaces.org/primeng-v13-lts/#/table/filter
Angular version
15
PrimeNG version
13
Build / Runtime
Angular CLI App
Language
TypeScript
Node version (for AoT issues node --version)
18
Browser(s)
No response
Steps to reproduce the behavior
1 go to https://www.primefaces.org/primeng-v13-lts/#/table/filter
2 go to the section 'Filter Row'
3 filter with 'Xuxue Feng' agent and use 'Ukraine' in country.
4 Try to change filter agent --> It's impossible to see and use the filter
Expected behavior
No response
The text was updated successfully, but these errors were encountered: