Entire DOMBrowser stack

Entire DOMBrowser stack. This CL is the entire DOMBrowser stack in a single set
so that reviewers can reference what I am doing in sub-CLs. This CL will not be
committed, so review should occur on the sub-CLs. I will attempt to keep this
up to date with the changes occuring in other reviews, but it might be out of
date. Don't take it as canon if there is a sub-CL.

Patch from Ryan Harrison <rharrison@chromium.org>;

BUG=none
TEST=none

[Nikita (slow), 2011-02-28 14:13:43]

For a long term solution think about a way to combine OOBE / sign in on a single
HTML page so that transitions between screens happen without page reload.

Welcome > EULA > Update (if none) > Sign in.

All should be just divs with CSS transitions.

[Nikita (slow), 2011-02-28 14:16:25]

To simplify understanding of the whole design, please create a simple diagram /
description how all classes interact.

[rharrison, 2011-02-28 19:09:37]

On 2011/02/28 14:16:25, Nikita Kostylev wrote:
> To simplify understanding of the whole design, please create a simple diagram
/
> description how all classes interact.

I have created a document that covers what I am attempting to do with the
DOMBrowser stack and why. I have shared it with all of the people that I think
would be immediately interested in it. If you cannot access, please contact me.

[commit-bot: I haz the power, 2011-03-03 17:07:40]

No LGTM from valid reviewers yet.

[rharrison, 2011-03-03 17:07:59]

On 2011/03/03 17:07:40, commit-bot wrote:
> No LGTM from valid reviewers yet.
My bad, clicked commit on the wrong CL