AndroidOverlay implementation using Dialog.

media/mojo/interfaces/android_overlay.mojom

 // Copyright 2017 The Chromium Authors. All rights reserved.
 // Use of this source code is governed by a BSD-style license that can be
 // found in the LICENSE file.
 
 module media.mojom;
 
 import "media/mojo/interfaces/media_types.mojom";
 import "mojo/common/unguessable_token.mojom";
 import "ui/gfx/geometry/mojo/geometry.mojom";
 
@@ skipping 38 matching lines @@
 struct AndroidOverlayConfig {
   // |routing_token| provides the client with an opaque handle that will attach
   // an overlay to a the correct WindowAndroid.  Typical usage is that a
   // RenderFrameHostImpl will provide this token to the RenderFrame.  When the
   // overlay is created, the WindowAndroid that currently hosts the render frame
   // will be the parent of the overlay.  For legacy reasons, we need this token
   // to be sent via IPC, so using the message pipe, or other mojo construct, as
   // the identifier won't work yet.
   mojo.common.mojom.UnguessableToken routing_token;
 
+  // Initial rectangle.
   gfx.mojom.Rect rect;
+
+  // Is a secure overlay required, such as for displaying protected content?
+  bool secure;
 };