-
Notifications
You must be signed in to change notification settings - Fork 4.6k
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
TypeError: Cannot read properties of undefined (reading 'style') at FrozenColumn.updateStickyPosition #10794
Comments
I cloned this project and tried to add a condition to and it works fine
|
I have the same problem too. |
The |
Hi @tamvcspk, Thanks for your report and suggestion. |
Hi @yigitfindikli, thanks for fixing this. Will it be fixed also for version 12.2.x ? In my project I don't want to update to V13 yet. |
Hi @antsteyer, Fixed 12.2.3 too. |
If you have a PrimeNG PRO Support subscription please post your issue at;
https://pro.primefaces.org
where our team will respond within 4 business hours.
If you do not have a PrimeNG PRO Support subscription, fill-in the report below. Please note that
your issue will be added to the waiting list of community issues and will be reviewed on a first-come first-serve basis, as a result, the support team is unable to guarantee a specific schedule on when it will be reviewed. Thank you for your understanding.
Current Queue Time for Review
Without PRO Support: ~8-12 weeks.
With PRO Support: 1 hour
I'm submitting a ... (check one with "x")
Plunkr Case (Bug Reports)
Please demonstrate your case at stackblitz by using the issue template below. Issues without a test case have much less possibility to be reviewd in detail and assisted.
https://stackblitz.com/github/primefaces/primeng-issue-template
Current behavior
The console will throw the following error if there are more than 1 columns with
pFrozenColumn
along with empty message template.It happened because the index of
filterRow.children[index]
is null inupdateStickyPosition
function. The emptymessage template has only 1td
element.This might cause the table's filter global to work incorrectly.
Expected behavior
Minimal reproduction of the problem with instructions
https://stackblitz.com/edit/github-dmm8bb?file=src%2Fapp%2Fapp.component.html
What is the motivation / use case for changing the behavior?
Please tell us about your environment:
Language: [all | TypeScript X.X | ES6/7 | ES5]
Node (for AoT issues):
node --version
=The text was updated successfully, but these errors were encountered: