Whoops, forgot to add the stack trace. I was in the IRC channel a while ago when I was told in no uncertain terms that "ng-repeat has nothing to do with jquery so...".
This stack trace shows otherwise: <https://lh5.googleusercontent.com/-WKtW_TKyzOI/VIdleHi5SjI/AAAAAAAAG8s/StfGL9pZga8/s1600/stack.png> On Tuesday, December 9, 2014 10:44:28 AM UTC-10, Cory Blissitte wrote: > > I have an ng-repeat <tr> that is populating a table. The table headers > are setup with ng-clicks that change the sort predicate and direction, and > the ng-repeat has the sort predicate and direction defined in it. Sorting > works. On clicking a table header, the rows are sorted correctly. The > exception however breaks other things in the page since execution stops. > > > It appears that the problem is that this Sizzle.attr function is being > called on each row, and then it gets to the 'end ngRepeat' row, it flips > out because it is not actually an HTML element (it is a comment). > > <!-- end ngRepeat: contest in AllContests | orderBy:sort:ReverseSort --> > > Has anyone previously experienced this? > > > <https://lh6.googleusercontent.com/-XW4goj9dVfA/VIddxjZsJgI/AAAAAAAAG8Q/euVOtw5_VQg/s1600/sizzle.png> > > <https://lh3.googleusercontent.com/-NvEqPxyok9o/VIddWusdJmI/AAAAAAAAG8I/J8mXdTqF2C4/s1600/ng-repeat.png> > > <https://lh3.googleusercontent.com/-JLZdQ5LUz2k/VIde0VBaBVI/AAAAAAAAG8c/NCKucEfwl7g/s1600/Sorting%2BFunction.png> > > -- You received this message because you are subscribed to the Google Groups "AngularJS" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/angular. For more options, visit https://groups.google.com/d/optout.
