Skip to content

[web] Unify configuration into a single entrypoint. #114701

@ditman

Description

@ditman

As part of #114700, an opportunity showed up to unify/clean up the multiple window global objects into a unified API to pass configuration from JS to the engine.

We should attempt to unify all the global configuration entrypoints into the same API, so all the data passed from JS ends up in the engine as part of the configuration FlutterConfiguration object. See configuration.dart.

Docs

  • See: (Stretch) Unify JS Configuration section in the design doc

Metadata

Metadata

Assignees

Labels

P1High-priority issues at the top of the work listc: tech-debtTechnical debt, code quality, testing, etc.e: flutter.jsIssues with Flutter web custom initialization through JS APIsengineflutter/engine related. See also e: labels.platform-webWeb applications specifically

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions