MD Settings: Separate code to be loaded lazily to its own lazy_load.html

MD Settings: Separate code to be loaded lazily to its own lazy_load.html

This CL does not change the way the advanced page is loaded. It is still loads
during startup as before. This is a preparatory step/trick, that allows landing
all the BUILD configuration changes first, before dealing with the lazy loading logic.

BUG=597347
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:closure_compilation

Review-Url: https://codereview.chromium.org/2746033005
Cr-Commit-Position: refs/heads/master@{#457574}
Committed: https://chromium.googlesource.com/chromium/src/+/06614e256a13dd528d165d33c30c158f225834d7

[dpapad, 2017-03-15 00:42:24]

Description was changed from

==========
MD Settings: Separate lazy loaded code to lazy_load.html

Currenty lazy_load.html is loaded similarly as before (not lazily).

BUG=597347
==========

to

==========
MD Settings: Separate lazy loaded code to lazy_load.html

Currenty lazy_load.html is loaded similarly as before (not lazily).

BUG=597347
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:closure_compilation
==========

[dpapad, 2017-03-15 00:53:23]

Description was changed from

==========
MD Settings: Separate lazy loaded code to lazy_load.html

Currenty lazy_load.html is loaded similarly as before (not lazily).

BUG=597347
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:closure_compilation
==========

to

==========
MD Settings: Separate lazy loaded code to lazy_load.html

This CL does not change the way lazy_load.html is loaded, it is still loaded
during startup as before. This is a preparatory step/trick, that allows landing
all the BUILD configuration changes first, before dealing with the way the
lazy module is loaded.

BUG=597347
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:closure_compilation
==========

[dpapad, 2017-03-15 00:53:46]

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

[commit-bot: I haz the power, 2017-03-15 00:54:14]

Dry run: CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[dpapad, 2017-03-15 00:55:01]

Description was changed from

==========
MD Settings: Separate lazy loaded code to lazy_load.html

This CL does not change the way lazy_load.html is loaded, it is still loaded
during startup as before. This is a preparatory step/trick, that allows landing
all the BUILD configuration changes first, before dealing with the way the
lazy module is loaded.

BUG=597347
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:closure_compilation
==========

to

==========
MD Settings: Separate code to be loaded lazily to its own lazy_load.html

This CL does not change the way lazy_load.html is loaded, it is still loaded
during startup as before. This is a preparatory step/trick, that allows landing
all the BUILD configuration changes first, before dealing with the way the
lazy module is loaded.

BUG=597347
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:closure_compilation
==========

[commit-bot: I haz the power, 2017-03-15 01:01:47]

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

[dpapad, 2017-03-15 02:56:18]

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

[commit-bot: I haz the power, 2017-03-15 02:56:55]

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-03-15 04:25:51]

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

[commit-bot: I haz the power, 2017-03-15 04:25:52]

Dry run: This issue passed the CQ dry run.

[dpapad, 2017-03-15 07:38:44]

Description was changed from

==========
MD Settings: Separate code to be loaded lazily to its own lazy_load.html

This CL does not change the way lazy_load.html is loaded, it is still loaded
during startup as before. This is a preparatory step/trick, that allows landing
all the BUILD configuration changes first, before dealing with the way the
lazy module is loaded.

BUG=597347
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:closure_compilation
==========

to

==========
MD Settings: Separate code to be loaded lazily to its own lazy_load.html

This CL does not change the way the advanced page is loaded. It is still loads
during startup as before. This is a preparatory step/trick, that allows landing
all the BUILD configuration changes first, before dealing with the lazy loading
logic.

BUG=597347
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:closure_compilation
==========

[dpapad, 2017-03-15 07:38:58]

dpapad@chromium.org changed reviewers:
+ dbeam@chromium.org

[Dan Beam, 2017-03-15 16:26:07]

lgtm

[dpapad, 2017-03-15 17:20:55]

On 2017/03/15 at 16:26:07, dbeam wrote:
> lgtm

Thanks. This CL depends on the Vulcanize patch CL,
https://codereview.chromium.org/2733143002. I'll ping them again today, see if
they can give an ETA for the PR merge. If I can't reach them, I'll just send
https://codereview.chromium.org/273314300 for review too.

[dpapad, 2017-03-16 20:48:18]

The CQ bit was checked by dpapad@chromium.org

[commit-bot: I haz the power, 2017-03-16 20:48:42]

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-03-16 21:53:10]

CQ is committing da patch.

Bot data: {"patchset_id": 40001, "attempt_start_ts": 1489697298951860,
"parent_rev": "8ac49009bba02f67c1ff5382a8caae70f14fec2f", "commit_rev":
"06614e256a13dd528d165d33c30c158f225834d7"}

[commit-bot: I haz the power, 2017-03-16 21:54:00]

Description was changed from

==========
MD Settings: Separate code to be loaded lazily to its own lazy_load.html

This CL does not change the way the advanced page is loaded. It is still loads
during startup as before. This is a preparatory step/trick, that allows landing
all the BUILD configuration changes first, before dealing with the lazy loading
logic.

BUG=597347
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:closure_compilation
==========

to

==========
MD Settings: Separate code to be loaded lazily to its own lazy_load.html

This CL does not change the way the advanced page is loaded. It is still loads
during startup as before. This is a preparatory step/trick, that allows landing
all the BUILD configuration changes first, before dealing with the lazy loading
logic.

BUG=597347
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:closure_compilation

Review-Url: https://codereview.chromium.org/2746033005
Cr-Commit-Position: refs/heads/master@{#457574}
Committed:
https://chromium.googlesource.com/chromium/src/+/06614e256a13dd528d165d33c30c...
==========

[commit-bot: I haz the power, 2017-03-16 21:54:02]

Committed patchset #3 (id:40001) as
https://chromium.googlesource.com/chromium/src/+/06614e256a13dd528d165d33c30c...