Closed
Bug 1506476
Opened 6 years ago
Closed 4 years ago
Add support for containers to browser.startup.homepage
Categories
(Firefox :: Security, defect)
Tracking
()
RESOLVED
INVALID
People
(Reporter: diafygi, Unassigned)
References
()
Details
Attachments
(2 files)
User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:63.0) Gecko/20100101 Firefox/63.0 Steps to reproduce: 1. Enable Multi-Account Containers 2. Set example.com to always open in a Container B 3. Set example.com as the Custom URL homepage in browser.startup.homepage (or via Preferences > Home > Homepage and new windows > Custom URLs) Actual results: Situation 1 (incorrect behavior): 1. Close Firefox. 2. Open Firefox. 3. Homepage opens to example.com, but not in Container B 4. Refresh the page. 5. A new tab opens in Container B with example.com as url. Situation 2 (correct behavior): 1. Have Firefox open. 2. Click the Home icon in the top toolbar. 3. A new tab opens in Container B with example.com as url. Expected results: 1. When opening Firefox for the first time, Custom URLs for the homepage should open in their default containers. NOTE: This may be security issue since it means urls you expected to open in a specific container is now leaked to your main tabs. 2. The browser.startup.homepage field in about:config should allow to manually specify containers in which to open the urls. For example: browser.startup.homepage = "https://google.com|https://example.com/" Should be able to do something like: browser.startup.homepage = "https://google.com|{ContainerB}https://example.com/" Open to suggestions on what the notation syntax should be.
Comment 1•6 years ago
|
||
I've tested this on latest FF 63 and 64, but I couldn't reproduce it. I've set google.com to always open in Personal container, also set it as homepage in browser.startup.homepage. Following the STR from Situation 1, I'm asked in which container I want to open it after restarting the browser(see my attachment). Could you provide some additional information in order to reproduce it? Thank you!
Flags: needinfo?(diafygi)
Reporter | ||
Comment 2•6 years ago
|
||
I created a 90 second screen capture video showing how to reproduce the issue on a new firefox profile (Firefox 63, Xubuntu 16.04).
Flags: needinfo?(diafygi)
Comment 3•5 years ago
|
||
I'm setting the component, in order to involve the development team reviewing this. Feel free to change it to a more appropriate one, if I'm wrong.
Component: Untriaged → Security
Reporter | ||
Comment 4•5 years ago
|
||
I just updated to 66.0.1 (64-bit) Mozilla Firefox for Ubuntu canonical - 1.0, and domains now open in their correct containers. Not sure what changed in the latest update, but you can now mark this issue as resolved.
Reporter | ||
Comment 5•5 years ago
|
||
I just updated to 67.0 (64-bit) Mozilla Firefox for Ubuntu canonical - 1.0, the bug is back. Urls in browser.startup.homepage setting do not automatically open in their containers.
Reporter | ||
Comment 6•4 years ago
|
||
This bug still persists in Firefox 72.0
Comment 7•4 years ago
|
||
Re-filed in the multi-account-containers GitHub issues list, since that's where the extension is maintained: https://github.com/mozilla/multi-account-containers/issues/1801
Status: UNCONFIRMED → RESOLVED
Closed: 4 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•