Skip to content

Representing stub implementations of APIs which confuse feature detection #6636

@foolip

Description

@foolip

Unfortunately it happens that browsers ship stub implementations of APIs that either do nothing, or throw exceptions. Such APIs appear to be there when doing feature detection, but can't actually be used.

Per Non-functional defined names imply partial_implementation these should be represented using partial_implementation, typically with notes explaining the situation.

The problem with this is that web developers really can't use these APIs, they don't work partially. APIs like this are worse than no support, as they confuse feature detection.

Examples of these:

Please add to the list or comment, if there are enough that would raise the priority of this issue.

Metadata

Metadata

Assignees

No one assigned

    Labels

    data:apiCompat data for Web APIs. https://developer.mozilla.org/docs/Web/APIidleIssues and pull requests with no recent activity

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions