Skip to content

Report app page lifecycle events through FDC3 for Web protocols to enable DAs to improve HeartBeat Handling #1703

Description

@kriswest

Enhancement Request

Use Case

Modern browsers manage page lifecycles (which can throttle or halt javascript execution within an app window when it is hidden). Events are available through the Page Lifecycle browser API which inform the application of changes in its status.

A browser-based desktop agent cannot currently listen for these events for windows within its scope. The addition of events to the Web Connection Protocol WCP or Desktop Agent Communication Protocol should be explored to allow reporting of state changes to the Desktop Agent which would allow them to develop better logic for handling heartbeats and intent resolution (to throttled or frozen apps).

See #1686 for the original discussion of the issue

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions