-
Notifications
You must be signed in to change notification settings - Fork 2.5k
UI Grid Logs Warn messages when hiding a column (angular.js:12330 Trying to focus on an element that isn't an element) #5206
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
Comments
The same issue is happening to me. |
+1 any solution guys? |
Guys, this 'warning' still hapen on version ui-grid - v4.0.3... |
This issue can sometimes be reproduced on a grid without data and appears to cause the column menu to not show up. |
I'm using AngularJS 1.6.7 and ui-grid 4.1.3 and I'm having the same issue. Even more, with versions of angular > 1.6 I think it' s causing this error : "Possibly unhandled rejection: not-element". You can reproduce with this plunkr : http://plnkr.co/edit/BUybCa9ADfx4rH7gEDNH when you hide a column. Hope it' s gonna be fixed soon, it's not really nice to make workarounds to avoid this error. |
I am using AngularJS 1.6.7 and ui-grid 4.2.0 , facing same issue. Trying to focus on an element that isn't an element. Is there any workaround for now ? |
Is anyone still seeing this in v4.6.2? |
@georgiabarnes Yes I'm still seeing it on v4.6.2 and AngularJS v1.7.2, Was it meant to be fixed? |
Issue is more a "heads-up" than an actual bug as I believe functionality of the grid is unaffected.
However, if you open up the following Tutorial (http://ui-grid.info/docs/#/tutorial/102_sorting) and open up the browser console and hide any of the columns in any of the sample tables, you get the warning message below:

You can see 4 times ui-grid is trying to focus on a null or non-angular element.
I've seen this "warning" occur on all UI-grids in all the tutorials (as well as my app which is where I first found it and thought perhaps I was doing something "inappropriate").
The text was updated successfully, but these errors were encountered: