Skip to content

PointerEvents coming from the engine need to contain view id #112205

@goderbauer

Description

@goderbauer

In a world where we have more then one view, the PointerEvents need to contain the view ID from which they originated from so they can be dispatched to the right place in the framework.

Metadata

Metadata

Assignees

No one assigned

    Labels

    P3Issues that are less important to the Flutter projecta: multi windowIssues related to multi window supportc: new featureNothing broken; request for a new capabilityengineflutter/engine related. See also e: labels.frameworkflutter/packages/flutter repository. See also f: labels.team-engineOwned by Engine teamtriaged-engineTriaged by Engine team

    Type

    No type

    Projects

    Status

    Done

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions