groovecoder

(Someone from Firefox here)

It's a popular request; about as popular as everyone who wants Ctrl+T to open in the default container. :)

So, for our core experience we picked the default behavior that helps maximize the privacy and security protections of Containers.

The good news is that, with the contextualIdentities extension API (exclusive to Firefox!), add-on authors can make their own add-ons to change this behavior. Like Taborama is doing:

https://github.com/kesselborn/taborama

Check out https://developer.mozilla.org/Add-ons/WebExtensions/API/cont... for more info on making Container-aware extensions.

Another good idea. I filed an issue in the repo for this. Add +1's here:

https://github.com/mozilla/testpilot-containers/issues/343

You're right. We keep control over the experiments so that we know the consistency of the data we're measuring.

A problem with using our full release channel Telemetry is that so many users have so many variables it's hard to compare apples to apples. E.g., was their performance issue caused by a setting, an add-on, the site they were on, or Firefox itself?

Test Pilot experiments give us some controls and parameters on the experience so we have a clearer idea of what's causing what.

That's a neat idea. Is there a bug for it in bugzilla?

Can you run the "Pulse" experiment and provide feedback on the sites that are slow and/or broken? We will use that data to help debug performance problems - especially the worst ones on popular sites.

https://testpilot.firefox.com/experiments/pulse

Independent of Containers in test pilot, we are planning to do a shield study with variations of privacy-related settings toggled for users, then measure and ask users how their web experience worked. The goal is to find improved privacy related settings that don't break the web for people.

You can keep track at https://arewewebextensionsyet.com/#addons

Great feedback. A segment of people seem do correlate windows with containers more easily than tabs. We are measuring both window & tab usage in the experiment to get a quantitative sense for it too.

I personally use Tab Groups add-on and associate each of my tab groups with a container, but I also mix my containers in a certain group. E.g., sometimes I'm on hacker news for fun, and sometimes I'm here for work. ;)

We are also hard at work supporting add-on authors porting to WebExtension APIs. I'm especially trying to help Privacy & Security add-on authors.

Just to be clear, this is NOT just a simple UI version of profiles. Containers only separate Cookies, localStorage, indexedDB, HTTP data cache, Image Cache (bug in progress), and other areas supported by originAttributes (See https://wiki.mozilla.org/Security/Contextual_Identity_Projec...)

I.e., Containers do NOT protect against some lower-level privacy vulnerabilities like plugin enumeration or history-sniffing that are mitigated more by using entirely separate profiles.

This is the most satisfying experience I have so far using Containers. :)

You can disable search engine suggestions in the Firefox Search preferences, if that's what you're worried about?

Neither location bar autocomplete nor form field autocomplete are separated by userContextId ... yet. See https://wiki.mozilla.org/Security/Contextual_Identity_Projec... for details.

We have an issue in the GitHub repo for this ... the more upvotes it gets, the more likely we will put it into a next release. :)

https://github.com/mozilla/testpilot-containers/issues/306

To fight distractions online and stay in a coding zone, I use RescueTime and set limits on time spent on distracting sites. Like hacker news. ;)

As a Mozillian who also cares very much about open standards, I agree. Google has both a long and recent track record of helping to advance open standards - CalDAV, WebRTC, WebM, etc. - and I have no doubt they will continue to do so - e.g., Physical Web.

However, Google's purpose in the world is not to advance open standards.

That is Mozilla's purpose. That's why this is a strategic, long-term decision on Mozilla's part. A world with a strong Google, strong Mozilla, and strong Yahoo (and Apple, and Microsoft, and Samsung, and Intel, etc.) is better for everyone.

A world where any one of those entities controls too much power is worse.

For me, I look forward to working with partners at Google and Yahoo.

Indeed - Yahoo is also powering Weather and Stocks apps on iOS. All the competition is good for everyone.

BTW, there are also some sweet new demos at https://developer.mozilla.org/demos/

We're working on this right now in #mdndev on irc.mozilla.org

We launched Kuma on August 3, 2012. That post is about the MDN redesign we launched in 2013.

No, see jvehent's comment:

"an automated data sanitization process failed, emails and salted hashed passwords were disclosed. no server was hacked."

The emails are customized for each type of affected user.

We are going to work on performance issues until EOY. If anyone would like to help, we're using a new label in GitHub for it:

https://github.com/mozilla/kuma/issues?labels=performance&pa...

Ooo, interesting. Now that we're on ES and have a real search index, we should try including code snippets as context when performing a search.

We can't generate the whole thing statically, because there are parts of the interface that change with user state.

We do render the HTML for article content, which includes many scripting templates.

We're seeing a lot of interest in the static/caching side of the site. I wonder if we should do a public article about it and invite people to help us improve it.

Yes, that's exactly what we do:

https://github.com/mozilla/kuma/blob/master/apps/wiki/models...

Hmm ... it should work that way now. In fact, only admin users can force a page to refresh its cached content.

Though we are getting a spike in traffic with the redesign launch, New Relic still reports app server response times of <600ms. But WebPagetest confirms really slow load times. [1]

If anyone finds some gross offenders of page performance, please file a bug: http://bugzilla.mozilla.org/form.mdn or better yet - send a pull request: https://github.com/mozilla/kuma !

[1] http://www.webpagetest.org/result/131209_Z0_1Q09/

Fixed. BTW, MDN is a wiki so if you see stuff like that again I think you can fix it yourself. :)

Oh, but if you're getting ISE's that's a bug. You can file those here:

http://bugzilla.mozilla.org/form.mdn

If you're signed in, you should have an option to make the page. MDN is a wiki. :)