I've run through a number of navigation test and cannot reproduce this on the latest build from the trunk. I ran the same tests against the Alpha 2 release and did notice the WARNING logging about null DOMs, etc. There were also some places where the navigation did a redirect instead of a foward but it seems to be working properly in the current code. I'm going to mark this as resolved - cannot reproduce. It's possible one or more changes we've made since Alpha 2 have fixed this but I haven't pinpointed anything specific.
If you the reporter could verify that this now working for them, please add a comment to the case. If it's still causing a problem, we'll need a specific test case to troubleshoot any further.
I've run through a number of navigation test and cannot reproduce this on the latest build from the trunk. I ran the same tests against the Alpha 2 release and did notice the WARNING logging about null DOMs, etc. There were also some places where the navigation did a redirect instead of a foward but it seems to be working properly in the current code. I'm going to mark this as resolved - cannot reproduce. It's possible one or more changes we've made since Alpha 2 have fixed this but I haven't pinpointed anything specific.
If you the reporter could verify that this now working for them, please add a comment to the case. If it's still causing a problem, we'll need a specific test case to troubleshoot any further.