1485582 - Multi-account containers: user typed location bar value (URL) gets lost when moving a tab to a different container

Status: NEW

(Firefox :: Tabbed Browser, defect, P3)

Description

[Daniel]

User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:61.0) Gecko/20100101 Firefox/61.0
Build ID: 20180704194802

Steps to reproduce:

Enter URL into location bar, but do not press enter.
Switch container for tab.



Actual results:

Container is switched.
URL is removed.


Expected results:

Container is switched.
URL is kept, so it's easy to confirm and open URL in new tab.

Comment 1

[Timea Cernea [:tbabos][inactive]]

Hi Daniel,

Thank you for the report!
If I understood correctly this issue can be reproduced by typing in the URL bar an address and switch to a container via the Multi-account Container addon ( Firefox Release).
The expected result would be that the typed address in the first tab to also appear in the newly opened tab via container. As I observed the addon will only open a new tab in a container without taking into account anything from the previously highlighted tab. Speaking of which, I am not entirely sure if it is bug or not.

However, I switched to the latest Firefox Nightly where we have containers by default. Since there is a "Reopen in Container" option for the tabs, I typed in an address in the search bar and reopened the tab in a container. As you mentioned, I expected that the typed address is kept in the newly opened container but it was not. Since any loaded page (ex: Facebook) will be loaded again if the tab is reopened in a container I am not sure if any typed address in the search bar should have the same behavior. 
Thus, I will set a component to involve the development team to review this issue.

Comment 2

[Daniel]

Hello,

This is mostly just a UX glitch. I can of course type URL, press enter to load and then switch container (while URL is still loading) and the new container will just reload the URL correctly. This however slows me down - because URL is basically loaded twice (first container, second container), even if not completely. 

My use case would allow to type URL, then switch container, without need for loading. This would bring slicker UX.

Comment 3

[Anton Karmanov]

Moreover if an URL has been "sent" (e.g. by Enter key) but a page is not loaded yet (e.g. because of poor bandwidth), opening the tab in an other container produces an empty URL tab.

From my perspective the new tab in a container should get the URL which user is seeing in the origin tab address bar.