Fixes crash on startup with compact nav. A recent change meant it's

Fixes crash on startup with compact nav. A recent change meant it's
possible for GetLocationBarView to be invoked before the compact nav
classes have been created. This makes sure we don't crash if that
happens.

BUG=89843
TEST=none
TBR=pkasting@chromium.org,stevet@chromium.org

Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=93545

[sky, 2011-07-22 04:13:21]

I landed this fix, but this is still very fragile. I'll see about doing a fix
that makes this unnecessary.

  -Scott

[SteveT, 2011-07-22 12:15:28]

LGTM

Out of curiosity, what was the change that introduced this crash?

On 2011/07/22 04:13:21, sky wrote:
> I landed this fix, but this is still very fragile. I'll see about doing a fix
> that makes this unnecessary.
> 
>   -Scott

[sky, 2011-07-22 15:34:53]

http://codereview.chromium.org/7358005/
The change made it so we can get a WM_MOVE earlier than we did before.

  -Scott

On Fri, Jul 22, 2011 at 5:15 AM,  <stevet@chromium.org> wrote:
> LGTM
>
> Out of curiosity, what was the change that introduced this crash?
>
> On 2011/07/22 04:13:21, sky wrote:
>>
>> I landed this fix, but this is still very fragile. I'll see about doing a
>> fix
>> that makes this unnecessary.
>
>>   -Scott
>
>
>
> http://codereview.chromium.org/7492005/
>

[Peter Kasting, 2011-07-22 18:06:00]

I'm wondering why we're still fixing compact nav code when we decided to abandon
it.  Shouldn't this have been removed already?  Who is responsible for that?

[SteveT, 2011-07-25 13:24:41]

I've filed a bug (crbug.com/89162) to track the removal of cnav. alcor@ and the
UI Leads wanted to take a different approach to compact nav, so we wanted to see
if some of this code can be reused.

I will chat with jeffreyc@ about pulling the flag so the first prototype is
inaccessible. Perhaps we'll also take the code out early as well, as there's
been no extra time spent on a new prototype yet.