kiosk: Skip LOGGED_IN_NOT_ACTIVE during app launch

kiosk: Skip LOGGED_IN_NOT_ACTIVE during app launch

Ash is changed that LOGGED_IN_NOT_ACTIVE is treated as
a non user blocking state so that browser windows during user
sign-in are can be activated before login screen is dismissed.
However a side effect of that is modal dialog under this state
will be placed in SystemModalContainer instead of
LockSystemModalContainer and causing the issue. The CL skips
LOGGED_IN_NOT_ACTIVE during app launch so that dialogs created
during the app launch are placed to the correct container.

BUG=727951
Review-Url: https://codereview.chromium.org/2915943002
Cr-Commit-Position: refs/heads/master@{#476327}
Committed: https://chromium.googlesource.com/chromium/src/+/aba83971264e7cdb32577693ef7f28953af5d2e9

[xiyuan, 2017-05-31 23:18:24]

The CQ bit was checked by xiyuan@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2017-05-31 23:19:03]

Dry run: CQ is trying da patch.

Follow status at:
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2017-05-31 23:50:07]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2017-05-31 23:50:08]

Dry run: This issue passed the CQ dry run.

[xiyuan, 2017-06-01 15:35:21]

xiyuan@chromium.org changed reviewers:
+ tbarzic@chromium.org

[xiyuan, 2017-06-01 15:35:22]

It is a band-aid for the kiosk regression. The requirements are conflicting with
each other for regular users and kiosk app launching. For regular users, we want
LOGGED_IN_NOT_ACTIVE to not blocking windows and things put behind the login
screen. But for kiosk app launching, the network config UI wants to be put on
top of the login screen. We need to merge this back to M60 so I want to keep the
CL simple here.

Let me know what you think. Thanks.

[tbarzic, 2017-06-01 16:31:42]

lgtm

[xiyuan, 2017-06-01 16:51:01]

The CQ bit was checked by xiyuan@chromium.org

[commit-bot: I haz the power, 2017-06-01 16:51:36]

CQ is trying da patch.

Follow status at:
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2017-06-01 16:57:00]

CQ is committing da patch.

Bot data: {"patchset_id": 1, "attempt_start_ts": 1496335861753780, "parent_rev":
"8a05953afa5a5f242d4f00fc994a3f3acab185e3", "commit_rev":
"aba83971264e7cdb32577693ef7f28953af5d2e9"}

[commit-bot: I haz the power, 2017-06-01 16:57:11]

Description was changed from

==========
kiosk: Skip LOGGED_IN_NOT_ACTIVE during app launch

Ash is changed that LOGGED_IN_NOT_ACTIVE is treated as
a non user blocking state so that browser windows during user
sign-in are can be activated before login screen is dismissed.
However a side effect of that is modal dialog under this state
will be placed in SystemModalContainer instead of
LockSystemModalContainer and causing the issue. The CL skips
LOGGED_IN_NOT_ACTIVE during app launch so that dialogs created
during the app launch are placed to the correct container.

BUG=727951
==========

to

==========
kiosk: Skip LOGGED_IN_NOT_ACTIVE during app launch

Ash is changed that LOGGED_IN_NOT_ACTIVE is treated as
a non user blocking state so that browser windows during user
sign-in are can be activated before login screen is dismissed.
However a side effect of that is modal dialog under this state
will be placed in SystemModalContainer instead of
LockSystemModalContainer and causing the issue. The CL skips
LOGGED_IN_NOT_ACTIVE during app launch so that dialogs created
during the app launch are placed to the correct container.

BUG=727951

Review-Url: https://codereview.chromium.org/2915943002
Cr-Commit-Position: refs/heads/master@{#476327}
Committed:
https://chromium.googlesource.com/chromium/src/+/aba83971264e7cdb32577693ef7f...
==========

[commit-bot: I haz the power, 2017-06-01 16:57:13]

Committed patchset #1 (id:1) as
https://chromium.googlesource.com/chromium/src/+/aba83971264e7cdb32577693ef7f...