Index: services/ui/public/interfaces/window_tree_constants.mojom |
diff --git a/services/ui/public/interfaces/window_tree_constants.mojom b/services/ui/public/interfaces/window_tree_constants.mojom |
index af7d9d0f0de03c267ecccf9f6c55c0b518be5bb4..c23d42d22c0191109cb3b5f861d38cdd8a611491 100644 |
--- a/services/ui/public/interfaces/window_tree_constants.mojom |
+++ b/services/ui/public/interfaces/window_tree_constants.mojom |
@@ -29,23 +29,6 @@ struct WindowData { |
bool visible; |
}; |
-// Each Window has support for two surfaces. Generally the |DEFAULT| surface |
-// is used. The |UNDERLAY| surface is useful if the owner of a window wants to |
-// to Embed() another client and at the same time draw something under the |
-// embedded apps representation. |
-// TODO(fsamuel): Remove this once window decorations are no longer underlay |
-// surfaces. http://crbug.com/647852. |
-enum CompositorFrameSinkType { |
- // Only the owner of a window may obtain this surface. |
- // The window manager can change the offset of this by way of |
- // SetUnderlaySurfaceOffsetAndExtendedHitArea(). |
- UNDERLAY, |
- |
- // Only the embedded app may obtain this surface. If an app is not embedded |
- // in the Window than the owner may also render to this surface as well. |
- DEFAULT, |
-}; |
- |
// The result of an input event sent to a client app. |
enum EventResult { |
HANDLED, |