Login on Embeded Wave redirects to Google Wave. Not Expected Behavior

[GoogleCodeExporter]

After the last unannounced update the behavior of the embed API has changed
in many unexpected ways!

In this case a user will go to the page with an embeded wave (which does
not allow anonymous posts or viewing) and see a blank wave with "Anonymous"
highlighted. (bad in itself)

A registered wave user can login using the login link. The logged in user
is then redirected to the original wave, in Gogole Wave away from the
original site with the embedded wave.

This is not the expected behavior! Once logged in the registered wave user
should STAY on the page with the embedded wave and allowed to interact with
the wave at that site. 

Is this not the whole purpose of an embedded wave??????

As a side note a text greeting or login box instructions or a greyed over
version of the text on the wave should or anything besides a blank wave
should great the user who is not logged in.

Original issue reported on code.google.com by bradjyo...@gmail.com on 24 Apr 2010 at 9:42

[GoogleCodeExporter]

Thanks for filing, I have reported both of the issues (anonymous screen/login 
redirect).

Original comment by pamela.fox on 29 Apr 2010 at 12:59

• Changed state: Confirmed
• Added labels: InternalWave-google.comw6ey_oQvVD, InternalWave-google.comw6ey_oQvVF

[GoogleCodeExporter]

I agree that the "Login" link should remember which page referred you, and then 
send
you back to that page once you've logged in. I'm trying to use this on an 
intranet
website and it's confusing the bejeebus out of our users. 

Original comment by suboscillator on 3 Jun 2010 at 4:27

[GoogleCodeExporter]

when I can see the fix to this bug. 

Original comment by vinaykatkar on 6 Jul 2010 at 5:55