Open Bug 1516455 Opened 6 years ago Updated 2 years ago

“Send Tab to Device” doesn't preserve container

Categories

(Firefox :: Firefox Accounts, defect, P3)

Product:
Firefox
Component:
Firefox Accounts
Type:
defect

Tracking

()

People

(Reporter: jld, Unassigned)

References

(Depends on 1 open bug)

Details

STR: with a container tab, use “Send Tab to Device” Expected: the other device opens the tab in the same container, at least if it exists on the device (e.g., if it's one of the default ones like “Personal”) Observed: the link is opened in a non-container tab -- I'm not sure what I'd expect for non-default containers. Matching by name seems reasonable for manually created containers, but for add-ons that auto-create temporary containers there's no reason why different browsers' "CG 1" "CG 2" "CG 3" etc. would have anything to do with each other. I also don't have a good idea about the UX for the case where the container state can't be preserved.
In a similar vein, one could argue that tabs sent from a Private Browsing window should open in a Private Browsing window on the target device.
We probably need to have the concept of a container exist across devices - just the name of the container probably isn't enough. Bug 1288858 has a lot of discussion around that.
Depends on: 1288858
Priority: -- → P3

(In reply to Ryan Kelly [:rfkelly] from comment #1)

In a similar vein, one could argue that tabs sent from a Private Browsing
window should open in a Private Browsing window on the target device.

This request keeps coming back. Hopefully, we can work on this later this year once we have solid components in place.

It's unclear how confusing the experience will be since mobile doesn't have containers but I'm sure we'll figure it out.

(In reply to Ryan Kelly [:rfkelly] from comment #1)

In a similar vein, one could argue that tabs sent from a Private Browsing
window should open in a Private Browsing window on the target device.

I totally agree. This one comes up a lot too.

The growing interest in Send Tab is exciting to see.

Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.