Skip to content

Optionally disable COEP/COOP headers from run command in WASM builds #163479

@martyfuhry

Description

@martyfuhry

Use case

I would like to be able to disable COEP/COOP headers while debugging WASM builds. In particular, this issue is blocking our project's adoption of WASM:

firebase/flutterfire#12819

Turning off headers will fix the functionality, but we have no way of turning them in debug mode, e.g., running:

$ flutter run -d chrome --wasm

Proposal

We would like to be able to optionally disable headers in debug mode from the command line, e.g.:

$ flutter run -d chrome --wasm --disable-headers

Metadata

Metadata

Assignees

No one assigned

    Labels

    P3Issues that are less important to the Flutter projectc: new featureNothing broken; request for a new capabilityc: proposalA detailed proposal for a change to Fluttere: wasmIssues related to the wasm build of Flutter Web.platform-webWeb applications specificallyteam-webOwned by Web platform teamtoolAffects the "flutter" command-line tool. See also t: labels.triaged-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