Expose container isolation in lightbeam

[jonathanKingston]

At some point we would like to show how containers are isolated in Lightbeam to demonstrate their advantage to solving tracking.

[groovecoder]

Luke idea: plug/promote/advertise Containers with a blurb like:

"Learn how Containers can isolate your browsing activity from trackers" + Faked/spoofed screenshot showing 4 separate smaller Lightbeam graphs instead of 1 big graph.

[clement-analogue]

So far, Lightbeam does not show containers at all. I think I saw a commit that remove them form visualization. So my Lightbeam so quite empty, only couple of websites, because all site I usually visits are assigned to their own containers, so sites visits from these containers are also in containers themselves, and I changed the behavior of the "+" button to add a new tab to display immediately the contextual menu for containers, so I rarely have a tab not in a container.

It would be nice to have the data from containers. It can be by having the lists of containers on the left panel, clicking on a container's name would do the same job as what is it doing now but for the selected container.

To really show the benefit of containers, it would be nice to have an overview with all data. To distinguish the containers, assigning the color of the container to the color of the dots. Because few containers will have the same color, maybe the "cloud" of dots of each container can be circled with its name displayed. It will stress their isolating function. Also, as different websites will appears in different containers, e.g. same website reached both from Facebook and Twitter containers, it can be a good idea to add between parenthesis the container's name beside the domain name.

[princiya]

@jonathanKingston @groovecoder any pointers to get started with this? this way I can get started with containers too :)

[jonathanKingston]

It's been a while since I have given this much thought however we will need to:

• Store requests by cookieStoreId
  • Tabs have this key however requests don't
• By default filter away cookieStoreId that isn't default
• Migrate existing data to new format
• Provide some temporary query string that can be used to filter by cookieStoreId until a UI is ready EG: index.html?cookieStoreId=firefox-container-1

@clement-analogue I agree with everything you said, I want it also however time is a limitation here really.

Also note that we don't show service workers still for the fact that cookieStoreId isn't in webRequests, fixing this would make the graph more complete.