Before the upgrade to 0.7 calling opensocial.requestNavigateTo with the canvas surface specified would work whether you were on the profile or the canvas.  It may seem like a silly thing to do, but without explaining my whole app I'll just say that it was useful to be able to do a requestNavigateTo the canvas from the canvas.

With the upgrade this no longer works.  Calling rNT from the canvas with the canvas surface specified doesn't do anything.  I'm sure I can figure out a way to accomplish what I was doing before without using rNT, but it would be really nice if it could still work.  Is there any specific reason it was disabled from working the way it use to?

Thanks 

I think that requestNavigateTo from the canvas to the canvas should definitely navigate to a new URL, so the appParams can get appended to it and users can copy and paste the URL in their address bar to link directly to specific pages in an app and bookmark and refresh them also.

 We're having to change our requestNavigateTo to simply putting the url of the app with appParams appended to it, since we used to use requestNavigateTo to handle pagination wthin our app. As phil mentioned, it's always nice to have a url to either pass around or let users bookmark to navigate directly to a specified resource.

Wayne:

 We're having to change our requestNavigateTo to simply putting the url of the app with appParams appended to it, since we used to use requestNavigateTo to handle pagination wthin our app. As phil mentioned, it's always nice to have a url to either pass around or let users bookmark to navigate directly to a specified resource.

You can't just change it to a normal link with the URL of the app plus appParams because your app isn't allowed to change the parent window URL.  If you do that, every time you click a link you'll wind up adding another full MySpace page within your app frame.  And it doesn't solve the issue of making the window URL copy-able for passing around.  Or am I misunderstanding how you're planning on working around this?

Can somebody from the MDP team please comment as to whether this is a temporary bug or a permanent situation as to how rNT will work? 

Mark:

You can't just change it to a normal link with the URL of the app plus appParams because your app isn't allowed to change the parent window URL.  If you do that, every time you click a link you'll wind up adding another full MySpace page within your app frame.  And it doesn't solve the issue of making the window URL copy-able for passing around.  Or am I misunderstanding how you're planning on working around this?

Can somebody from the MDP team please comment as to whether this is a temporary bug or a permanent situation as to how rNT will work? 

have you tried target="_top"?

 Regardless, I definitely echo the sentiment that it'd be nice to have someone from MDP shed some light on the situation :)

 target="_top" may work now, but I know for sure that they have said it will not be allowed in the real launch

 just jumping on this thread to say that this is a real problem for us as well...... especially since its already the 13th!!  anybody have any news about when this might get fixed?  

I agree with the posts above. I've used requestNavigateTo the same surface, and I found it very useful.

So, is this a bug or an expected behavior? If the former, will it get fixed, and if it's the latter, can we please have this functionality back?

bump

Can we please get an answer from the MDP team? 

+1

Seriously, this breaks canvas navigation *completely*. 

Bump again. 

Bumping until somebody from the MDP team can provide some sort of answer.  I think this will affect a lot of apps and their canvas links/navigation.  It's been 4 or 5 days since the functionality change and we still have no idea if this is permanent or a bug.

 This is a bug and has been fixed, I'm not sure of the exact timing but I think this will get up to the live site on Tuesday or Wednesday, if not, it'll be another week.  At that point you'll be able to rNT to the current view.

Fixed today!

Thanks