Make N-panel menus detachable as floating windows

Allow users to detach the N-panel (or individual tabs within it) from the 3D Viewport and float them as independent, draggable windows, freeing up canvas space without losing access to tools and properties.

The problem

The N-panel is one of Blender's most used UI surfaces, it houses object transforms, add-on tabs, and much more. But it comes with a significant trade-off: it always occupies a fixed slice of your viewport.

Users on single-monitor setups are forced to choose: keep the N-panel open and lose viewport real estate, or close it constantly and toggle it back with N every time. Neither is ideal for active workflows.

Even on multi-monitor setups, Blender currently has no way to send a panel to a secondary screen without duplicating the entire editor which is wasteful and cumbersome.

The proposal

Add the ability to detach the N-panel menu either the entire panel or individual tabs, into a standalone floating window that behaves like a native OS window. This window would:

• Be draggable and resizable, independently of the main Blender window
• Stay in sync with the viewport context (selected object, active scene, etc.)
• Be re-dockable back into the viewport when no longer needed
• Remember its last position and size between sessions (optional, as a preference)
• Triggered via the grabber icon that already exists at the top right of the N-panel menu, or via right-clicking a tab → "Detach tab".

Why this makes sense

• Reclaim 100% of your 3D canvas without closing the panel you're actively using.
• Park the panel on a second screen for a dedicated properties view, just like other pro DCC tools.
• Blender already supports floating render output windows and tearable editors, this is a natural extension of that system.
• Maya, Houdini, Cinema 4D and Substance Painter all support detachable/floating panels as a core UX feature.

Who benefits

This primarily helps single-monitor users who want to tweak transform values or add-on settings without shrinking their workspace, multi-monitor power users who want a dedicated panel screen, and heavy add-on users whose N-panel tabs have grown large (e.g. Geometry Nodes tools, rigging add-ons, etc.). It does not affect users who prefer the current docked behaviour , it would be strictly opt-in.

Implementation notes

Blender's windowing system already creates detached windows (e.g. for render output). Extending this to allow a panel region to be "torn off" into a bpy.types.Window -based floating container should be architecturally feasible. The panel would retain its region draw callbacks and RNA data bindings, the main challenge is ensuring the context pointer ( bpy.context ) correctly mirrors the active viewport. A Python add-on prototype could potentially validate the concept before committing it to core.

This could ship incrementally: first as a floating window tied to a specific workspace, then eventually with full multi-window session persistence.