:Gijs (he/him) Reporter
	Description • 8 years ago

The location bar is an annoying piece of UI that has to accomplish 3 conflicting tasks at once:

1) reflect what the currently loaded page is
2) allow the user to navigate to some other page
3) allow the user to navigate based on what is currently inside the URL bar (ie manipulate the URL in a way that is persistent)

The problematic state here is almost always "somewhere between page A and page B". That is, if the page that's currently visible (and/or running script, etc.) is page A, but the user elected to navigate to page B, which URL should be in the URL bar?

Generally speaking, the result depends on how you're moving from page A to page B:

- if you click a link on page A to load page B, we continue showing page A as long as it's loaded
- if you typed page B's URL in the URL bar and hit enter, we show page B
- if you dragged page B's URL to the URL bar, post-bug-791597, we show page A

This bug is about what to do in the "I right clicked in the URL bar and hit 'paste and go'" case. We currently show page B. Arguably, just like in the drag case, it might make sense to show page A to avoid spoofing attacks.

	Daniel Veditz [:dveditz]
	Comment 1 • 7 years ago

We do have "loading" animation, but the problem is it's tucked out of the way in the tab bar. In the URL bar itself we tend to remove the site identity block but that's pretty subtle. What if we added a loading animation to the URL bar itself when in the problematic state between A & B in place of the site identity block?