Introduce --remote-debugging-frontend switch for custom remote debugging front-end

Introduce --remote-debugging-frontend switch for custom remote debugging front-end

DevTools "hosted mode" is broken in a multiple ways:
- it uses sync XHR from inside the microtask (this was recentrly forbidden)
- as the protocol was split and moved around, the InspectorBackendHostedMode.js
  is not able to generate proper inspector backend commands

This patch introduces the --remote-debugging-frontend switch with a value of
a absolute path to devtools front-end checkout.

If the --remote-debugging-frontend switch is specified, then the remote
debugging session will be opened with the front-end loaded from the
specified endpoint.

We assume that this endpoint will be serving a simple check-out
of devtools front-end, which is missing generated files
InspectorBackendCommands.js and SupportedCSSProperties.js.
For this reason, requests to these files are fulfilled from the chrome
devtools bundled resources.

BUG=623602
R=dgozman

[lushnikov, 2016-06-30 16:45:55]

please, take a look

[lushnikov, 2016-06-30 16:51:02]

Description was changed from

==========
Introduce --devtools-frontend flag instead of pound for remote debugging

The hosted mode was broken in a multiple ways:
- it used sync XHR from inside the microtask (this was recentrly forbidden)
- as the protocol was split and moved around, the InspectorBackendHostedMode.js
  was not able to generate proper inspector backend commands

This patch introduces the --devtools-frontend flag which is used
to load a front-end for a remote debugging session. The old way of doing
this via the "#<url>" notion is removed.

BUG=623602
R=dgozman
==========

to

==========
Introduce --devtools-frontend switch to set custom remote debugging url

The hosted mode was broken in a multiple ways:
- it used sync XHR from inside the microtask (this was recentrly forbidden)
- as the protocol was split and moved around, the InspectorBackendHostedMode.js
  was not able to generate proper inspector backend commands

This patch introduces the --devtools-frontend switch which is used
to load a front-end for a remote debugging session. The old way of doing
this via the "#<url>" notion is removed.

If the --devtools-frontend switch was set, then the remote
debugging session will be opened with the front-end loaded from the
specified endpoint.

We assume that this endpoint will be serving a simple check-out of devtools
front-end, which is missing generated
files InspectorBackendCommands.js and SupportedCSSProperties.js.
For this reason, requests to these files are fulfilled from the chrome
devtools bundled resources.

BUG=623602
R=dgozman
==========

[lushnikov, 2016-06-30 16:51:30]

Description was changed from

==========
Introduce --devtools-frontend switch to set custom remote debugging url

The hosted mode was broken in a multiple ways:
- it used sync XHR from inside the microtask (this was recentrly forbidden)
- as the protocol was split and moved around, the InspectorBackendHostedMode.js
  was not able to generate proper inspector backend commands

This patch introduces the --devtools-frontend switch which is used
to load a front-end for a remote debugging session. The old way of doing
this via the "#<url>" notion is removed.

If the --devtools-frontend switch was set, then the remote
debugging session will be opened with the front-end loaded from the
specified endpoint.

We assume that this endpoint will be serving a simple check-out of devtools
front-end, which is missing generated
files InspectorBackendCommands.js and SupportedCSSProperties.js.
For this reason, requests to these files are fulfilled from the chrome
devtools bundled resources.

BUG=623602
R=dgozman
==========

to

==========
Introduce --devtools-frontend switch for custom remote debugging front-end

The hosted mode was broken in a multiple ways:
- it used sync XHR from inside the microtask (this was recentrly forbidden)
- as the protocol was split and moved around, the InspectorBackendHostedMode.js
  was not able to generate proper inspector backend commands

This patch introduces the --devtools-frontend switch which is used
to load a front-end for a remote debugging session. The old way of doing
this via the "#<url>" notion is removed.

If the --devtools-frontend switch was set, then the remote
debugging session will be opened with the front-end loaded from the
specified endpoint.

We assume that this endpoint will be serving a simple check-out of devtools
front-end, which is missing generated
files InspectorBackendCommands.js and SupportedCSSProperties.js.
For this reason, requests to these files are fulfilled from the chrome
devtools bundled resources.

BUG=623602
R=dgozman
==========

[lushnikov, 2016-06-30 16:52:04]

Description was changed from

==========
Introduce --devtools-frontend switch for custom remote debugging front-end

The hosted mode was broken in a multiple ways:
- it used sync XHR from inside the microtask (this was recentrly forbidden)
- as the protocol was split and moved around, the InspectorBackendHostedMode.js
  was not able to generate proper inspector backend commands

This patch introduces the --devtools-frontend switch which is used
to load a front-end for a remote debugging session. The old way of doing
this via the "#<url>" notion is removed.

If the --devtools-frontend switch was set, then the remote
debugging session will be opened with the front-end loaded from the
specified endpoint.

We assume that this endpoint will be serving a simple check-out of devtools
front-end, which is missing generated
files InspectorBackendCommands.js and SupportedCSSProperties.js.
For this reason, requests to these files are fulfilled from the chrome
devtools bundled resources.

BUG=623602
R=dgozman
==========

to

==========
Introduce --devtools-frontend switch for custom remote debugging front-end

The hosted mode was broken in a multiple ways:
- it used sync XHR from inside the microtask (this was recentrly forbidden)
- as the protocol was split and moved around, the InspectorBackendHostedMode.js
  was not able to generate proper inspector backend commands

This patch introduces the --devtools-frontend switch which is used
to load a custom front-end for a remote debugging session. The old way of doing
this via the "#<url>" notion is removed.

If the --devtools-frontend switch was set, then the remote
debugging session will be opened with the front-end loaded from the
specified endpoint.

We assume that this endpoint will be serving a simple check-out of devtools
front-end, which is missing generated
files InspectorBackendCommands.js and SupportedCSSProperties.js.
For this reason, requests to these files are fulfilled from the chrome
devtools bundled resources.

BUG=623602
R=dgozman
==========

[lushnikov, 2016-06-30 16:52:42]

Description was changed from

==========
Introduce --devtools-frontend switch for custom remote debugging front-end

The hosted mode was broken in a multiple ways:
- it used sync XHR from inside the microtask (this was recentrly forbidden)
- as the protocol was split and moved around, the InspectorBackendHostedMode.js
  was not able to generate proper inspector backend commands

This patch introduces the --devtools-frontend switch which is used
to load a custom front-end for a remote debugging session. The old way of doing
this via the "#<url>" notion is removed.

If the --devtools-frontend switch was set, then the remote
debugging session will be opened with the front-end loaded from the
specified endpoint.

We assume that this endpoint will be serving a simple check-out of devtools
front-end, which is missing generated
files InspectorBackendCommands.js and SupportedCSSProperties.js.
For this reason, requests to these files are fulfilled from the chrome
devtools bundled resources.

BUG=623602
R=dgozman
==========

to

==========
Introduce --devtools-frontend switch for custom remote debugging front-end

The hosted mode was broken in a multiple ways:
- it used sync XHR from inside the microtask (this was recentrly forbidden)
- as the protocol was split and moved around, the InspectorBackendHostedMode.js
  was not able to generate proper inspector backend commands

This patch introduces the --devtools-frontend switch which is used
to load a custom front-end for a remote debugging session. The old way of doing
this via the "#<url>" notion is removed.

If the --devtools-frontend switch is specified, then the remote
debugging session will be opened with the front-end loaded from the
specified endpoint.

We assume that this endpoint will be serving a simple check-out of devtools
front-end, which is missing generated
files InspectorBackendCommands.js and SupportedCSSProperties.js.
For this reason, requests to these files are fulfilled from the chrome
devtools bundled resources.

BUG=623602
R=dgozman
==========

[lushnikov, 2016-06-30 16:53:11]

Description was changed from

==========
Introduce --devtools-frontend switch for custom remote debugging front-end

The hosted mode was broken in a multiple ways:
- it used sync XHR from inside the microtask (this was recentrly forbidden)
- as the protocol was split and moved around, the InspectorBackendHostedMode.js
  was not able to generate proper inspector backend commands

This patch introduces the --devtools-frontend switch which is used
to load a custom front-end for a remote debugging session. The old way of doing
this via the "#<url>" notion is removed.

If the --devtools-frontend switch is specified, then the remote
debugging session will be opened with the front-end loaded from the
specified endpoint.

We assume that this endpoint will be serving a simple check-out of devtools
front-end, which is missing generated
files InspectorBackendCommands.js and SupportedCSSProperties.js.
For this reason, requests to these files are fulfilled from the chrome
devtools bundled resources.

BUG=623602
R=dgozman
==========

to

==========
Introduce --devtools-frontend switch for custom remote debugging front-end

The hosted mode was broken in a multiple ways:
- it used sync XHR from inside the microtask (this was recentrly forbidden)
- as the protocol was split and moved around, the InspectorBackendHostedMode.js
  was not able to generate proper inspector backend commands

This patch introduces the --devtools-frontend switch which is used
to load a custom front-end for a remote debugging session. The old way of doing
this via the "#<url>" notion is removed.

If the --devtools-frontend switch is specified, then the remote
debugging session will be opened with the front-end loaded from the
specified endpoint.

We assume that this endpoint will be serving a simple check-out
of devtools front-end, which is missing generated files
InspectorBackendCommands.js and SupportedCSSProperties.js.
For this reason, requests to these files are fulfilled from the chrome
devtools bundled resources.

BUG=623602
R=dgozman
==========

[lushnikov, 2016-06-30 16:54:36]

Description was changed from

==========
Introduce --devtools-frontend switch for custom remote debugging front-end

The hosted mode was broken in a multiple ways:
- it used sync XHR from inside the microtask (this was recentrly forbidden)
- as the protocol was split and moved around, the InspectorBackendHostedMode.js
  was not able to generate proper inspector backend commands

This patch introduces the --devtools-frontend switch which is used
to load a custom front-end for a remote debugging session. The old way of doing
this via the "#<url>" notion is removed.

If the --devtools-frontend switch is specified, then the remote
debugging session will be opened with the front-end loaded from the
specified endpoint.

We assume that this endpoint will be serving a simple check-out
of devtools front-end, which is missing generated files
InspectorBackendCommands.js and SupportedCSSProperties.js.
For this reason, requests to these files are fulfilled from the chrome
devtools bundled resources.

BUG=623602
R=dgozman
==========

to

==========
Introduce --devtools-frontend switch for custom remote debugging front-end

DevTools "hosted mode" is broken in a multiple ways:
- it uses sync XHR from inside the microtask (this was recentrly forbidden)
- as the protocol was split and moved around, the InspectorBackendHostedMode.js
  is not able to generate proper inspector backend commands

This patch introduces the --devtools-frontend switch which is used
to load a custom front-end for a remote debugging session. The old way of doing
this via the "#<url>" notion is removed.

If the --devtools-frontend switch is specified, then the remote
debugging session will be opened with the front-end loaded from the
specified endpoint.

We assume that this endpoint will be serving a simple check-out
of devtools front-end, which is missing generated files
InspectorBackendCommands.js and SupportedCSSProperties.js.
For this reason, requests to these files are fulfilled from the chrome
devtools bundled resources.

BUG=623602
R=dgozman
==========

[lushnikov, 2016-06-30 16:55:36]

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

[commit-bot: I haz the power, 2016-06-30 16:55:54]

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, 2016-06-30 16:59:43]

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

[commit-bot: I haz the power, 2016-06-30 16:59:44]

Dry run: Try jobs failed on following builders:
  ios-device on master.tryserver.chromium.mac (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.mac/builders/ios-device/builds...)

[lushnikov, 2016-07-01 01:51:48]

please, take another look!

[lushnikov, 2016-07-01 01:55:04]

Description was changed from

==========
Introduce --devtools-frontend switch for custom remote debugging front-end

DevTools "hosted mode" is broken in a multiple ways:
- it uses sync XHR from inside the microtask (this was recentrly forbidden)
- as the protocol was split and moved around, the InspectorBackendHostedMode.js
  is not able to generate proper inspector backend commands

This patch introduces the --devtools-frontend switch which is used
to load a custom front-end for a remote debugging session. The old way of doing
this via the "#<url>" notion is removed.

If the --devtools-frontend switch is specified, then the remote
debugging session will be opened with the front-end loaded from the
specified endpoint.

We assume that this endpoint will be serving a simple check-out
of devtools front-end, which is missing generated files
InspectorBackendCommands.js and SupportedCSSProperties.js.
For this reason, requests to these files are fulfilled from the chrome
devtools bundled resources.

BUG=623602
R=dgozman
==========

to

==========
Introduce --remote-debugging-frontend switch for custom remote debugging
front-end

DevTools "hosted mode" is broken in a multiple ways:
- it uses sync XHR from inside the microtask (this was recentrly forbidden)
- as the protocol was split and moved around, the InspectorBackendHostedMode.js
  is not able to generate proper inspector backend commands

This patch introduces the --remote-debugging-frontend switch with a value of
a absolute path to devtools front-end checkout.

If the --remote-debugging-frontend switch is specified, then the remote
debugging session will be opened with the front-end loaded from the
specified endpoint.

We assume that this endpoint will be serving a simple check-out
of devtools front-end, which is missing generated files
InspectorBackendCommands.js and SupportedCSSProperties.js.
For this reason, requests to these files are fulfilled from the chrome
devtools bundled resources.

BUG=623602
R=dgozman
==========

[lushnikov, 2016-07-01 03:41:56]

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

[commit-bot: I haz the power, 2016-07-01 03:42:05]

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, 2016-07-01 05:22:46]

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

[commit-bot: I haz the power, 2016-07-01 05:22:47]

Dry run: Try jobs failed on following builders:
  win_chromium_rel_ng on master.tryserver.chromium.win (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.win/builders/win_chromium_rel_...)

[pfeldman, 2016-07-02 05:49:42]

This goes a bit backwards - instead of steering the app towards being a
standalone reusable web-app, we rely more on the embedder.

[lushnikov, 2016-07-06 17:49:05]

True, unfortunately this patch doesn't help to achieve "stand-alone app" goal.

However, it helps to make DevTools easily hackable. I think these two goals
should be separate:

1. Stand-alone DevTools app
2. Lower DevTools contribution boundary

[pfeldman, 2016-07-06 17:50:44]

On 2016/07/06 17:49:05, lushnikov wrote:
> True, unfortunately this patch doesn't help to achieve "stand-alone app" goal.
> 
> However, it helps to make DevTools easily hackable. I think these two goals
> should be separate:
> 
> 1. Stand-alone DevTools app
> 2. Lower DevTools contribution boundary

I see these highly related if not matching.

[lushnikov, 2016-07-06 18:15:31]

I see a few properties where they differentiate: end users, internal structure
and build setup.

The "standalone DevTools app" properties:
- users: all web developers
- internal structure: aim for speed, sources are concatenated/optimized
- build: any. It might be tedious to build (comparable to Chrome), but as far as
  there's a pre-build version and distribution channel it's fine.

The "hackable DevTools" properties:
- users: web developers who want to contribute to DevTools
- internal structure: aim for debuggability. Sources are not optimized
- build: minimal/none. Ideally, it is just a github checkout.