Expand description
UI-thread task that actually creates a CEF browser pane.
Moved out of browser_panes.rs during Phase 3 of the pane modularization
split (see docs/specs/SPEC_BROWSER_PANE_MODULARIZATION.md §6). The task
structure here is a straight lift — same pre-flight checks, same
browser_host_create_browser call. BrowserPaneManager::create still
calls post_task(ThreadId::UI, ..) with an instance of this task; the
only change is the import path.
Dependencies (one-way, no cycle):
cef::*for CEF types and thewrap_task!macro.crate::state::AppStatefor the label queue and the Arc passed to the pane’s handler.crate::client::{AgentMuxHandler, AgentMuxClient}for the pane’s CEF client. Phase 4 will flip this direction by moving the pane callbacks intopane/callbacks.rs; until then,clientis fine as a one-way dependency.crate::commands::window::find_own_top_level_windowfor the parent HWND (CEF Views returns null on Alloy).