Closed Bug 1705992 Opened 4 years ago Closed 4 years ago

Multi-Account Containers weird behavior with Google products (Gmail, Drive)

Categories

(Core :: DOM: Security, defect)

Firefox 89
defect

Tracking

()

RESOLVED MOVED

People

(Reporter: sevastiyan.tsv, Unassigned)

References

Details

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:89.0) Gecko/20100101 Firefox/89.0

Steps to reproduce:

  1. Put Google web products to be opened by default on a Custom Container (e.g. Google)
  2. Write Gmail.com or Drive.com in address bar
  3. Enter
  4. Select Open in "Custom" Container.

Actual results:

Gmail:
400. That’s an error.
The server cannot process the request because it is malformed. It should not be retried. That’s all we know.

Drive:
Stuck inside Loop of open/close container tab.

Expected results:

Open Gmail normally.
Open Drive normally.

I deleted the Custom container and created a new one.
Added the Google and Gmail and Drive again.
Logged in with personal account (google account).
Gmail continues to get 400 error, but Drive seems to be opening normally now.

The Bugbug bot thinks this bug should belong to the 'Core::Networking: HTTP' component, and is moving the bug to that component. Please revert this change in case you think the bot is wrong.

Component: Untriaged → Networking: HTTP
Product: Firefox → Core

I think DOM:Security should be the right component for container-related bugs.
Feel free to change if I was wrong. Thanks.

Component: Networking: HTTP → DOM: Security

Thanks for reporting this. Multi-account container bugs are actually handled in the github repository. Bugzilla is used only for bugs in the underlying "originAttributes" implementation that powers Containers and Private Browsing separation, but that doesn't appear to be involved here.

It looks like this has already been noted in that project: https://github.com/mozilla/multi-account-containers/issues/2021

If you think your bug is different please file another issue there, or comment on that issue.

Status: UNCONFIRMED → RESOLVED
Closed: 4 years ago
Resolution: --- → MOVED
You need to log in before you can comment on or make changes to this bug.