User reported in an AMO review that disabling the Test Pilot extension didn't revert the change to the blank tab page caused by the New Tab Multivariate study. We've tested that the temporary add-on is removed if the user opts out of the individual study, but of course a lot of users' first thought would be to disable Test Pilot as a whole through the add-on manager, which doesn't give the cleanup routine a chance to run. A possible solution is to require that any temporary add-on installed for the purpose of an A/B test must include code that checks on startup whether Test Pilot is running so that it can disable itself if Test Pilot has also been disabled.
A change has been made to the New Tab Multivariate study add-on in version 1.3 to implement this behavior, and deployed to the server. People who join the study from now on will get this version, which means if they disable/remove Test Pilot their new tab will go back to normal. Unfortunately there doesn't seem to be any way to deploy 1.3 to users who started the study earlier and got version 1.2.
When we make Test Pilot restartless, we can try to handle this stuff in the disable() and remove() handlers in bootstrap.js.
Product: Mozilla Labs → Mozilla Labs Graveyard
Status: NEW → RESOLVED
Last Resolved: 2 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.