-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
Data-table scroll disappears when filtering in a field shown by width scroll #1805
Comments
same situation. |
same situation with primeng@4.0.0 stable |
Hi does anyone got the solution for this. |
Same bug here |
Got the solution...just fix the width of datatable . |
@vermashailesh can you kindly elaborate/exemplify? you mean set a CSS style-width attribute over the p-datattable? |
This patch fixed that for me: .ui-datatable-scrollable-body |
@cagataycivici Can you elaborate on how your patch fixes this? The above fix from i0natan doesn't work. Setting |
I resolved this using some javascript code. var element = document.querySelectorAll('.ui-table-unfrozen-view') //In css file Hope this helps.. |
This might fix your issue. .ui-table-scrollable-wrapper { .ui-table-scrollable-header, .ui-table-scrollable-body, .ui-table-scrollable-footer { |
[x ] bug report => When filtering a field in the last columns in a data-table that has width scroll, the data table hide the shown column and I am not able to return to the column to filter again.
Current behavior
ERROR: the scroll disappear and show only the columns that were visible initially ( without scrolling ), and does not permit to see the field I filtered with and clear the content to show my records again.
Expected behavior
To be able to scroll, see and write again in the field after filter in it, when I get a non record results
Angular version: 2.1.2
PrimeNG version: 1.1.4
Browser: [all | Chrome XX | Firefox XX | IE XX | Safari XX | Mobile Chrome XX | Android X.X Web Browser | iOS XX Safari | iOS XX UIWebView | iOS XX WKWebView ]
Language: [all | TypeScript X.X | ES6/7 | ES5]
The text was updated successfully, but these errors were encountered: