-
Notifications
You must be signed in to change notification settings - Fork 29.7k
Closed
Labels
P2Important issues not at the top of the work listImportant issues not at the top of the work listc: new featureNothing broken; request for a new capabilityNothing broken; request for a new capabilityengineflutter/engine related. See also e: labels.flutter/engine related. See also e: labels.frameworkflutter/packages/flutter repository. See also f: labels.flutter/packages/flutter repository. See also f: labels.
Description
We should provide an API with the following features:
- The embedder can ask an engine to render in a new location, and expose that location as a new window to an existing isolate. The engine would provide the embedder with a token representing that window.
- In dart:ui, the Window subclass would be split into two in a super/subclass relationship. Most things would be on the subclass, which we'd continue to use for the window global.
- In dart:ui, there'd be an API to obtain the Window for a particular token.
- All Windows would have a
rendermethod, much like today. We'd also need to do per-window hit testing, accessibility, and other such things.
Metadata
Metadata
Assignees
Labels
P2Important issues not at the top of the work listImportant issues not at the top of the work listc: new featureNothing broken; request for a new capabilityNothing broken; request for a new capabilityengineflutter/engine related. See also e: labels.flutter/engine related. See also e: labels.frameworkflutter/packages/flutter repository. See also f: labels.flutter/packages/flutter repository. See also f: labels.