CrOS - Fix flaky FileManagerDialogTest

CrOS - Fix flaky FileManagerDialogTest

We were not waiting for the file manager extension to initialize its
Web Worker process before starting the test, which lead to occasional
crashes if the test completed before the init was done.

BUG=chromium:89733
TEST=browser_tests --gtest_filter=FileManagerDialogTest.* --gtest_repeat=10 --gtest_shuffle

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

[James Cook, 2011-08-08 18:28:11]

Robert, PTAL.  I left the call to postMessage('initialized', [regex]) instead of
converting to an object because we can just add more items to that array in the
future and they get mapped nicely to function arguments in file_manager.js.  It
seemed like what we did elsewhere.

[James Cook, 2011-08-08 19:17:35]

On 2011/08/08 18:28:11, James Cook (Chromium) wrote:
> Robert, PTAL.  I left the call to postMessage('initialized', [regex]) instead
of
> converting to an object because we can just add more items to that array in
the
> future and they get mapped nicely to function arguments in file_manager.js. 
It
> seemed like what we did elsewhere.

I renamed the message to "worker-initialized" as we discussed.  How's it look
now?

[rginda, 2011-08-08 19:18:45]

LGTM

On 2011/08/08 19:17:35, James Cook (Chromium) wrote:
> On 2011/08/08 18:28:11, James Cook (Chromium) wrote:
> > Robert, PTAL.  I left the call to postMessage('initialized', [regex])
instead
> of
> > converting to an object because we can just add more items to that array in
> the
> > future and they get mapped nicely to function arguments in file_manager.js. 
> It
> > seemed like what we did elsewhere.
> 
> I renamed the message to "worker-initialized" as we discussed.  How's it look
> now?