Skip to content

capi should absorb "Couldn't send status" error #131

@jcjones

Description

@jcjones

image

Since the CAPI doesn't currently use the receiver-end status channel, it's immediately dropped, and errors get logged to the console in Firefox. While Firefox isn't ready to use the messages, we should bitbucket them instead of letting errors log.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions