Gulde: So i added {timeout:15000} inside fetch and everything is good now
Rizor: Personally I’d just use the whatwg-fetch polyfill *shrug*
Derobles: I now see canceled in chrome dev tools
Desue: Ok, I’ll google that later
Sieloff: But you are exactly right, our rest api call is not timing out
Slanker: I was thinking that a library should be able to make another request if it didn’t get a response. Or is it our job to write that functionaliy
Rizor: That’s your job – if a library just did it, it could really ***** you up if the request isn’t idempotent and both end up going through
Vandeberg: How can i tell jquery to find the $”td /” which has a specific ID?
Rizor: Unless the lib were to cancel and retry I guess
Galimi: Yeah, that’s what I was thinking too
Hatto: Not really sure what’s wrong here. http://jsfiddle.net/vinex08/sf33z88e/ help please?
Chehab: So I guess, it’s nice to add that timeout:15000 I was playing with and just retry
Rizor: Giraffe_: $’td#’ + yourId if the id is a variable
Pommer: And that implies the / Rizor ?
Rizor: Honestly not even the td matters. IDs are all unique in html
Swaggert: Anything is an element
Rizor: So you can just look for the id
Swaggert: Are _supposed_ to be unique
Garfunkel: Cl***es are shared yeah
Morrissette: Wait i thought it was the otherway around
Rizor: Yeah. if they aren’t unique, that’s against spec and stuff should be expected to break
Barmes: I have few ***ignment to do tonight 😀 a whatwg-fetch polyfill b study bind again
Henderlight: Either way, the reason im being safe is because there are sorting options for multiple tables
Rizor: No. cl***es can be on multiple elements, IDs should be unique to a single element
Gerrero: Rizor: Element.id – Web API Interfaces MDN https://developer.mozilla.org/en-US/docs/Web/API/Element/id
Dering: I was looking at your code again – this.item.fetch.donethis.renderItem.bindthis, this.item I’m now wondering why we our developer used Underscore’s bind
Rizor: Zumba_ad_: are you comfortable with .call?
Polintan: Not yet, but i read few examples today and I see how it works
Dulek: It’s somewhat similar to bind
Rizor: Because bind’s arguments signature is pretty much the exact same thing as call, only instead of calling the function with a set “this” and the supplies arguments, it returns a new function that has those things pre-set for you and on which you can supply any additional arguments if you want/need to
Valderrama: Though the example i found today, I was told that it was a very bad example
Morey: Thank you Rizor, I’ll rest for now. I’ll study again later : Thank you so much!
Rizor: There are some really bizarre tricks you can do with both .call and .bind. If you can figure out why THIS works, then you’ll understand both:
Brauning: I’m starting to understanding this well
Dechellis: If we don’t do var self = this, it will point to global
Stirling: That was really weird
Wadell: Seems like you don’t have to worry about that on ES6
Innocent: But i think it’s still nice to learn because it will help us troubleshooting existing es5 apps
Rizor: Var slice = Function.prototype.call.bindArray.prototype.slice; var obj = {0: ‘foo’, 1: ‘bar’}; function show { return slicearguments; }; show’foo’,’bar’,’baz’;
Gerrero: Rizor: object ‘foo’, ‘bar’, ‘baz’
Comes: Let me paste that in my console
Rizor: Bind is so popular that ES7 is gonna have special syntax for it
Torkelson: I put a // in front and it still worked :
Courcelle: Is .call always and only used with .prototype?