Skip to content

☂️ Migration to multi-window API #60131

@gspencergoog

Description

@gspencergoog

This is a tracking bug for tracking the migration steps for implementing the multi-window API described in this design doc.

The steps for migration are:

  • Convert engine internals to an API that understands multiple windows/screens, but only supports one one window.
  • Convert the dart:ui Dart classes to use the internal engine API, but still only supports one window.
  • Add platform detection of screens on the platform, reporting the proper size for the screens that the window appears on (still only managing one screen and one window)
  • Add platform support for multiple screens and one window
  • Add support for creating multiple windows, allowing creation and disposal, but not reconfiguration.
  • Add support for re-configuring windows.

The initial PRs for the first step are flutter/engine#18368 and #57178

Metadata

Metadata

Assignees

Labels

P2Important issues not at the top of the work lista: desktopRunning on desktopa: multi windowIssues related to multi window supportc: new featureNothing broken; request for a new capabilitycustomer: alibabaengineflutter/engine related. See also e: labels.frameworkflutter/packages/flutter repository. See also f: labels.

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions