Issues with child navigation example firing only once about pym.js HOT 7 CLOSED

Do those pages (101 and 102) also add the event listener for navigation? After page load, the child's JS context will be blown away, and the original listener won't be valid anymore.

from pym.js.

Yes, the pym child code is identical on all pages (it's actually just one page called with different parameters). I also setup a simpler test case with 3 static pages with distinct names (foo1.html, foo2.html, etc.) and get the same results. Adding debugging to the child shows nothing on the subsequent hits.

This is in the client now for testing:

      console.log('recvd msg');
      console.log(url);

edit: actually here's a public test case - very simple example, not even cross-domain:
https://sporklab.com/pym/

from pym.js.

So it looks to me like what's happening is that your new child doesn't have an ID set, and as a result it's not matching the message regex that Pym uses to filter its own messages out of everything that can come through window.onmessage. Try to set a new ID manually when creating the child, so that it stays consistent, and I think it'll work. Unfortunately, due to the way that Pym constructs itself (as a closure, not as a class or prototype), this can be tough to debug. Sorry about that!

Edit to add: The initial message regex is /^pymxPYMxcw_quotegenxPYMx(\S+)xPYMx(.*)$/, and your second window has a regex of /^pymxPYMxundefinedxPYMx(\S+)xPYMx(.*)$/. I think configuring your child with an ID of "cw_quotegen" during initialization will work, but I haven't tried that.

from pym.js.

You may also want to investigate using Sidechain, our successor to Pym, which uses JSON sentinel values instead of regex matching and probably would be easier to get working.

from pym.js.

Are you saying to create the child like this?

var pymChild = new pym.Child('cw_quotegen');

from pym.js.

I believe it's an object param, so more like var pymChild = new pym.Child({ id: "cw_quotegen" }).

from pym.js.

That did it! Thanks. Sidechain looks interesting, but a bit too complex for our one-off use.

Now I just have to wait for someone in another timezone in Norway to update the client code on the real page. :)

from pym.js.