Commit e3dbd56f authored by Pavel Feldman's avatar Pavel Feldman Committed by Commit Bot

DevTools: add more docs for IsBrowserTargetDiscoverable to avoid confusion.

Change-Id: I9feee0a202323ec4fce650f2042c24880ff485a0
Reviewed-on: https://chromium-review.googlesource.com/663528Reviewed-by: default avatarDmitry Gozman <dgozman@chromium.org>
Commit-Queue: Dmitry Gozman <dgozman@chromium.org>
Cr-Commit-Position: refs/heads/master@{#501496}
parent 5eea3cdc
...@@ -59,8 +59,13 @@ class CONTENT_EXPORT DevToolsManagerDelegate { ...@@ -59,8 +59,13 @@ class CONTENT_EXPORT DevToolsManagerDelegate {
// Returns frontend resource data by |path|. // Returns frontend resource data by |path|.
virtual std::string GetFrontendResource(const std::string& path); virtual std::string GetFrontendResource(const std::string& path);
// Returns true for browsers running in the controlled environment that allow // Makes browser target easily discoverable for remote debugging.
// remote debugging. // This should only return true when remote debugging endpoint is not
// accessible by the web (for example in Chrome for Android where it is
// exposed via UNIX named socket) or when content/ embedder is built for
// running in the controlled environment (for example a special build for
// the Lab testing). If you want to return true here, please get security
// clearance from the devtools owners.
virtual bool IsBrowserTargetDiscoverable(); virtual bool IsBrowserTargetDiscoverable();
virtual ~DevToolsManagerDelegate(); virtual ~DevToolsManagerDelegate();
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment