I suspect the issue here is that the browser restores the last visible URL rather than the last committed URL - this *should* be fixed when bug 1353143 lands (and the equivalent webbrowser-app parts land)
I suspect the issue here is that the browser restores the last visible URL rather than the last committed URL - this *should* be fixed when bug 1353143 lands (and the equivalent webbrowser-app parts land)