Handful of related instant changes:

Handful of related instant changes:
. Makes the code for running the promo more real. We're not ready to
  flip it on yet, so it isn't enabled.
. Nukes verbatim from about:flags and instead randomly chooses
  verbatim/predictive when the user opts in. We're doing this to try
  and see if we get feedback as to which one folks like more. Windows
  preferences shows you which one you get (by way of an obscure
  label). I'll change gtk do to that shortly too.
. Adds metrics.

And a couple of random style issues I encountered in some files.

BUG=NONE
TEST=NONE

[Evan Stade, 2010-11-15 19:59:23]

lgtm

http://codereview.chromium.org/5023001/diff/2001/chrome/browser/instant/insta...
File chrome/browser/instant/instant_controller.cc (right):

http://codereview.chromium.org/5023001/diff/2001/chrome/browser/instant/insta...
chrome/browser/instant/instant_controller.cc:46: // kInstantWasEnabledOnce was
added after instant, set it now to make sure
nit: kInstantEnabledOnce

http://codereview.chromium.org/5023001/diff/2001/chrome/browser/instant/insta...
chrome/browser/instant/instant_controller.cc:82:
UMA_HISTOGRAM_CUSTOM_COUNTS(name, delta.InHours(), 1, 30 * 24, 50);
so the idea is we're tracking how long people leave it enabled?

[sky, 2010-11-15 20:15:26]

http://codereview.chromium.org/5023001/diff/2001/chrome/browser/instant/insta...
File chrome/browser/instant/instant_controller.cc (right):

http://codereview.chromium.org/5023001/diff/2001/chrome/browser/instant/insta...
chrome/browser/instant/instant_controller.cc:82:
UMA_HISTOGRAM_CUSTOM_COUNTS(name, delta.InHours(), 1, 30 * 24, 50);
On 2010/11/15 19:59:23, Evan Stade wrote:
> so the idea is we're tracking how long people leave it enabled?

Yes.