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
Including ui.grid.cellNav in your module, but not placing ui-grid-cellNav on a grid, causes many behind-the-scenes Javascript errors (for example, when you scroll the grid you get complaints "TypeError: Cannot read property 'getFocusedCell' of undefined").
Can this be fixed, or is there a workaround? Is there something I could/should do with respect to this sentence in the tutorial: "gridOptions.onRegisterApi callback to register the on_cellNav event and log when the cell is navigated"?
BTW, I'm in this situation because I have different grids on multiple sub-pages. On one of them I do not include the ui-grid-cellNav because I use RowTemplate to enable an ng-click for the entire row, and ui-grid-cellNav interferes with that. I've seen a separate issue where ui-grid-cellNav maybe didn't used to interfere with ng-click in the rowTemplate, and so if that were resolved, this would not be a problem for me (although it does seem like something that should be fixed anyway).
The text was updated successfully, but these errors were encountered:
Dev63
changed the title
Include ui.grid.cellNav in module but ui-grid-cellNav on table causes errors
Include ui.grid.cellNav in module but not ui-grid-cellNav on table causes errors
Nov 17, 2014
Thanks for posting this - I was getting "TypeError: Cannot read property 'getFocusedCell' of undefined" whenever I was scrolling through a table with my mousewheel. I had left ui.grid.cellNav in my module but wasn't using it anymore anywhere in my app. Once I took it out, the error went away when I scrolled through the table.
TypeError: Cannot read property 'getFocusedCell' of undefined
at /angular-ui-grid/ui-grid.js:11418:48
at Scope.$broadcast (/angular/angular.js:13070:28)
at self.fireScrollingEvent.gridUtil.throttle.trailing (/angular-ui-grid/ui-grid.js:2959:16)
at runFunc (/angular-ui-grid/ui-grid.js:9274:12)
at /angular/angular.js:14394:28
at completeOutstandingRequest (/angular/angular.js:4411:10)
at /angular/angular.js:4725:7
This happens only when the 'ui.grid.cellNav' module is included in the app AND the 'ui-grid-cellNav' directive is not included in the markup.
Including ui.grid.cellNav in your module, but not placing ui-grid-cellNav on a grid, causes many behind-the-scenes Javascript errors (for example, when you scroll the grid you get complaints "TypeError: Cannot read property 'getFocusedCell' of undefined").
Can this be fixed, or is there a workaround? Is there something I could/should do with respect to this sentence in the tutorial: "gridOptions.onRegisterApi callback to register the on_cellNav event and log when the cell is navigated"?
BTW, I'm in this situation because I have different grids on multiple sub-pages. On one of them I do not include the ui-grid-cellNav because I use RowTemplate to enable an ng-click for the entire row, and ui-grid-cellNav interferes with that. I've seen a separate issue where ui-grid-cellNav maybe didn't used to interfere with ng-click in the rowTemplate, and so if that were resolved, this would not be a problem for me (although it does seem like something that should be fixed anyway).
The text was updated successfully, but these errors were encountered: