Views does not support use of “CefWindowInfo.SetAsChild(parent_hwnd, …)”; or, in other words, creating a browser window directly as a child HWND. In your case it sounds like you might be creating cefsimple as a normal top-level window and then using WinAPI to reparent that HWND to some other window. That may work with Views (with or without Chrome runtime) at first glance, but some things (like focus, activation, etc) may exhibit problematic edge cases.
Okay I checked the code again. Even though I pass --use-views --hide-overlays --hide-controls --enable-chrome-runtime flag, we have removed views related logic. We use
CefBrowserHost::CreateBrowser API to create browsers. We always create browsers as child window as we call setAsChild method before CreateBrowser. Since the parent window doesn't have any decorations, I don't need to worry about them when such URLs are loaded.
However, for popup windows, the reparenting is done using WinAPI after popup CefBrowser has been created. Thus in these scenarios, I don't have a way to hide WS_OVERLAPPEDWINDOW decorations and address bar and other controls that come with --enable-chrome-runtime. So is there any workaround for the same?