1718599 - The "Firefox Home" page opens in Facebook container

Status: RESOLVED MOVED

(Core :: Security, defect)

Description

[zegkljan]

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:90.0) Gecko/20100101 Firefox/90.0

Steps to reproduce:

• set the home page as "Firefox Home"
• have Facebook container allowed
• open a tab with Facebook - it should be in Facebook container
• click the "Home" button - that takes you to the "Firefox Home" page

Actual results:

The "Firefox Home" page remains in Facebook container.

Expected results:

The "Firefox Home" page should not be in the Facebook container, as it is not part of Facebook.

Comment 1

[Peter Magyari (Desktop QA)]

Hi,

I was able to reproduce this issue on Firefox 89 and Firefox Nightly 91.0a1

I'm setting a component in order to get this issue looked at by the development team.

Thank you for reporting!

Comment 2

[Luca Greco [:rpl] [:luca] [:lgreco]]

This can be reproduced even without any extension if the user contexts are enabled directly from the about:config prefs.

Personally I do also think that pressing the home button should load the about:home page into a non-containerized tab, but that would be something that the about:home button should take care of (likely from inside the BrowserHome function defined in browser.js).

Moving to the "Firefox :: General" bugzilla component to be triaged from a Firefox Desktop perspective.

Comment 3

[Dave Townsend [:mossop]]

Not sure where container bugs are meant to go.

Comment 4

[(inactive) Nihanth Subramanya [:nhnt11]]

Luke, does this look like something we want to e.g. track in GitHub?

Comment 5

[Danny Colin [:sdk]]

Personally I do also think that pressing the home button should load the about:home page into a non-containerized tab

:rpl IMO, we shouldn't open it in a non-containerized tab since the user didn't explicitly asked to change context. We should only switch context if the user assigned their homepage to a specific container in the case that they use a custom homepage url. If they use the default New Tab, it should also stick to the current usercontext especially that we'd be open, on the addon side, to support a different homepage per container.

Luke, does this look like something we want to e.g. track in GitHub?

Since it mentions Facebook Container (addon), I'll consider this as a bug that should be moved. We can always re-open a new one if we want to take a decision on the Home button itself.