Little OT Dolby: I saw your.

Petrocco: EGreg, could you call a callback inside the iframe that is a reference to he parent window?

Rodrigues: To javascript inside an iframe

Rutter: Window.parent.myCallback // call inside iframe

Schorder: Mbrzuzy: yes but how do I uniquely identify the callback in the parent window

Ornelaz: P*** the name in via a query parameter or something.

Thanos: There might be more than one request outstanding, though.

Ornelaz: This sounds like not a very sane way of doing this though

Kopka: I really would prefer to keep this client side

Benanti: It’s perfectly sane to keep client side things client-side

Ornelaz: Yeah that’s still client side

Kochkodin: And not have the server receive the name of a callback

Ornelaz: Then use postmessage to send the callback name.

Muhs: Yes I can of course maintain a heap of callbacks, and p*** the index to the server

Deedrick: Hmm interesting idea. I can use iframe.onload, and the parent window will run code to call a function in the iframe

Musgraves: I’m not sure I understand how these two differ.

Ornelaz: Fwiw i don’t think this is a good idea. it would be simpler to just have the content in the iframe post a message up to the parent and have the parent call the funciton you need.

Pietsch: That sounds like a good idea

Nace: Isn’t that usally how it works? That way it will call it exactly when it’s loaded

Ornelaz: Or whenever it needs to do the call

Ornelaz: It also works if you ever do need to load it cross domain.

Vanderschaege: Is that what the ***ertionError means?

Ornelaz: That means you faile a unit test

Kassing: But does it mean the two values are not equal?

Kenagy: I know i failed a unit test; what i don’t understand is how

Ornelaz: Are you comparing objects with == or ===?

Konopacki: Tcsc: SyntaxError: syntax error

Marchaland: I am using ***ert.equal

Ornelaz: I guess you want to do ***ert.deepEqual

Stampka: That sounds like the exact opposite of what i want

Ornelaz: It will compare the values

Rochez: I thought deepEqual was === and equal was ==

Blenner: I was wrong : thanks!

Hoerger: I’m new to unit testing, thanks

Farone: Does ***ert.equal use ===?

Ornelaz: Yes but it isn’t equivalent to ***erting v1 === v2

Lineberger: Best to read the do***entation to find out.

Stefan: Or possibly read the code. ***ertion libraries aren’t /that/ hard to read.

Ornelaz: It recursively compares what’s in the two objects to find out if they have the same data

Ornelaz: I’m speculating but, thats almost certainly what it does

Sinnett: I now have a window.result = function { } inside the iframe

Zellous: And onload I just check that synchronously :

Mayeaux: Does anyone know how to turn off joined/left messages?

Bortle: Gregsometimes: depends on your discussion client

Morton: Some have no way of turning it off

Terrone: He’s using mIRC. There’s a setting for that.

Stauss: Gregsometimes: this might help you:

Brodzik: New to mIRC, but not to JavaScript.

Wescovich: Anyone here know how to wait for a new element to appear before capturing it’s text content? I’m using PhantomJS, trying to get new messages.

Dubas: Little OT Dolby: I saw your link on and my books says exatly what you wrote. Their definitions are not standard