Closed glockjt closed 10 years ago
Which version of backgrid are you using and are you using any custom cells?
This issue has been fixed last year. @glockjt let me know if you still have this problem.
Does this fiddle demonstrate the problem?:
Another example with no extra plugins:
http://jsfiddle.net/gdw2/61v9r02z/6/
The gotcha here is that I'm rendering two backgrids, replacing the first with the second. If I grid1.remove() the first (see fiddle), then it works fine. I'm guessing its best-practice to .remove()
views. Can anybody speak to this? Is it okay that this is necessary?
I have a view that initially renders a new Backgrid.Grid then I have an event listener listen for another's view state change (its a drop down box, so I listen for the change event). When a selection is made that views event listener triggers an event for the view containing the backgrid. The event listener of the view containing the backgrid filters the collection and uses the filtered collection to create a new Backgrid.Grid. When a cell is clicked in this backgrid it results in the above error on exit of the cell. Below is the code of the view containing the backgrids, if you need more code let me know. Thanks in advance.