Skip to content

[cross_file] [web] Separate "Save As" implementation details from XFile web class #91400

@ditman

Description

@ditman

The current implementation of the cross_file class for web deals with a "DOM Element" _target that is used to inject some DOM required to Save a XFile As... here.

That functionality should be stripped out of the XFile to a helper object (similar to everything else that is DOM-related), and the XFile delegate itself to this DOM helper when it needs to save:

  /// Saves the data of this CrossFile at the location indicated by path.
  /// For the web implementation, the path variable is ignored.
  @override
  Future<void> saveTo(String path) async {
    domHelper.saveFileAs(this, path);
  }

Metadata

Metadata

Assignees

No one assigned

    Labels

    P3Issues that are less important to the Flutter projectp: cross_fileThe cross_file pluginpackageflutter/packages repository. See also p: labels.platform-webWeb applications specificallyteam-webOwned by Web platform teamtriaged-webTriaged by Web platform team

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions