Repository navigation
Open
Labels
P3Issues that are less important to the Flutter projectIssues that are less important to the Flutter projecta: desktopRunning on desktopRunning on desktopa: multi windowIssues related to multi window supportIssues related to multi window supportc: new featureNothing broken; request for a new capabilityNothing broken; request for a new capabilitycustomer: chalk (g3)customer: crowdAffects or could affect many people, though not necessarily a specific customer.Affects or could affect many people, though not necessarily a specific customer.engineflutter/engine related. See also e: labels.flutter/engine related. See also e: labels.platform-linuxBuilding on or for Linux specificallyBuilding on or for Linux specificallyplatform-macosBuilding on or for macOS specificallyBuilding on or for macOS specificallyplatform-windowsBuilding on or for Windows specificallyBuilding on or for Windows specificallyteam-frameworkOwned by Framework teamOwned by Framework teamtriaged-frameworkTriaged by Framework teamTriaged by Framework team
Description
See discussion in google/flutter-desktop-embedding#98
If we end up supporting multiple root views within one engine instance, this will require embedding API changes. If we don't, we'll need to have a viable strategy to recommend for coordinating between windows that works for cases that require constant synchronization (e.g., a tools palette in one window, with the canvas using those tools in another)
Reacted by nesscx, Christoph Jerolimov, Sacchi, Modestas Valauskas, François Pluchino, Kab-yeon Lee, Saniko, Sacha Arbonel, Ivan, Oliver Welther and 465 more
Reacted by Leon, Eerey Solutions, talon12431, Xujiewan99, Domingo, Tech-Tac, Cruvie Kang, SmartVive, Omar Gylyjov and Israel Agoeiro
Reacted by Max Chertov, Rody Davis, mono — Masayuki Ono, Steven Spiel, TJB-99, Wolfgang Steiner, Ken, Maximilian Mitchell, Sahaj Rana, Théophile O. and 61 more
Reacted by Markus Hopfenspirger, AlbertInRC, Dmytro Hryppa, Reinier Millo Sánchez, Timothy Ojo, Eerey Solutions, Andrew Ares, Kristijan Žic, Aditya Dwivedi, Ardeshir Nahavandi Fard and 14 more
Reacted by Md. Rashidul Hasan, Max Chertov, Zero, Joanna May, Tom Chai, Taiju.Liu, CloudWebRTC, mono — Masayuki Ono, Eerey Solutions, J and 47 more
Reacted by nesscx, Geert-Johan Riemer, Emrah Bilbay, Ivan, Max Chertov, Rody Davis, mono — Masayuki Ono, TJB-99, Wolfgang Steiner, Parcool Tan and 84 more
Metadata
Metadata
Assignees
Labels
P3Issues that are less important to the Flutter projectIssues that are less important to the Flutter projecta: desktopRunning on desktopRunning on desktopa: multi windowIssues related to multi window supportIssues related to multi window supportc: new featureNothing broken; request for a new capabilityNothing broken; request for a new capabilitycustomer: chalk (g3)customer: crowdAffects or could affect many people, though not necessarily a specific customer.Affects or could affect many people, though not necessarily a specific customer.engineflutter/engine related. See also e: labels.flutter/engine related. See also e: labels.platform-linuxBuilding on or for Linux specificallyBuilding on or for Linux specificallyplatform-macosBuilding on or for macOS specificallyBuilding on or for macOS specificallyplatform-windowsBuilding on or for Windows specificallyBuilding on or for Windows specificallyteam-frameworkOwned by Framework teamOwned by Framework teamtriaged-frameworkTriaged by Framework teamTriaged by Framework team
Type
Projects
- StatusShow more project fieldsIn Progress
Activity
rodydavis commentedon May 2, 2019
Maybe as a proof concept we could start with alert popups that open a separate window and can be dragged.
Maybe like a Cupertino popover since they carry their own navigation internally on iPads.
https://gist.github.com/AppleEducate/6f2a1188d6256b0eff79131891ce92f1
stuartmorgan-g commentedon May 2, 2019
The place to start is agreement on, and design for, the technical approach that will be used to support multiple windows on desktop. A proof of concept can't come before a decision on what to build.
rodydavis commentedon May 2, 2019
Very true. 👍🏼
handicraftsman commentedon May 11, 2019
In OpenGL applications there is a need to call a method called like
MakeContextCurrent(different in every windowing API), thus i think it would be a nice idea to have some keyed contexts whose keys can be sent to the embedder to switch to the context. Although there is a problem with event handling - embedders would need to translate internal window system ids into context keys so flutter understands which window should receive the event. That means that both flutter and embedder must have 1-2 maps to identify the context keys.GregorySech commentedon Aug 26, 2019
Does this have any implication on how web handles multiple tabs?
171 remaining items
stan-at-work commentedon Feb 4, 2025
stuartmorgan-g commentedon Feb 4, 2025
FMorschel commentedon Feb 4, 2025
stan-at-work commentedon Feb 4, 2025
orestesgaolin commentedon Oct 27, 2025
For anyone getting redirected here from this error message:
This is how you enable windowing feature flag:
kaduvert commentedon Jun 4, 2026
some error logs on GNOME/wayland with the example from above:
logs
recording of how the logs came about to aid with diagnosing:
multiple.windows.mp4
orestesgaolin commentedon Jun 17, 2026
Support for multiple windows has gotten pretty solid recently. I built a demo using LLM and must admit this looks really promising.
feat: demo experimental de multiventana (windowing) para macOS
Gorniv commentedon Sep 1, 2026
Thanks for publishing Introducing the Desktop Windowing API for Flutter. I couldn’t find the article linked in this tracking issue, so I’m adding it here for subscribers who may have missed it.
One migration question for apps currently using
window_manager: the experimental API shown in the article covers title, size, constraints, activation, maximize/minimize/fullscreen, and window lifecycle, but I couldn’t find per-window equivalents for:getPosition)setPosition/setBounds)onWindowMoved)These capabilities are important for persisting and restoring each window’s placement, especially in multi-monitor setups.
window_managerprovides them for the existing main/implicit window, but it doesn’t appear to provide a migration path for every framework-created window.Are per-window position/bounds APIs and move notifications planned? Where a platform does not allow applications to control absolute window placement, best-effort semantics or an explicit unsupported result would still be useful, along with guidance on whether applications should temporarily retain
window_manageror native platform code.stan-at-work commentedon Sep 1, 2026
mauricev commentedon Sep 1, 2026
Plus the ability to open a window hidden (transparent windows, too?) and of course the black window bug on Mac OS, #184701 (comment)
saviq-work commentedon Sep 2, 2026
The approach we're taking is more towards abstracting higher level functionality away. So as an app developer, you wouldn't
get/setPosition(exactly because not all platforms support it, by design - and what even is the position in a AR/VR environment?). You can already control child window placement via the positioner interfaces. Instead of global positioning, we'll add functionality to automatically restore window positions on platforms that need it - and defer to the system where that's the platform's approach.Similarly, for window move events - those have to be limited to relative positions in parent/child relationships rather than global positions, the primary use case being docking/undocking toolboxes within the main window.
For hidden / transparent windows, it would be great to understand the use cases so we can design it well.
So generally when discussing these, would you please file separate feature requests for higher level functionality and add as many use cases you can think of. Add the
a: multi windowlabel so it doesn't get lost.Thanks for the feedback, all!
mauricev commentedon Sep 2, 2026
I create a feature request here, #192188, but I don't see how to add the proper label.
Razorex001 commentedon Sep 5, 2026
@saviq-work I can provide a real example of hidden/transparent windows use case in private, if you want.
In my case I had to opt for a hybrid design based on what I understood possible currently, so in my app I have the overlay surface created through Flutter’s multi-window api, but transparency, always-on-top, no-activate, click-through, reveal/hide, and cursor polling are implemented with native Win32 code.
I would have preferred if all what I needed could have been supported in flutter as part of the higher level functionality you were talking about.
It's a bit hard for me to file proper issues for these though as I don't really want to share details of my project publicly at the moment.