Skip to content

Add back APIs that are on the standard track even if they're not supported by all browsers #209

Closed
@srujzs

Description

@srujzs

I thought this was being tracked in a previous bug somewhere, but can't find it.

Currently, we only emit members that are supported on all 3 browsers and are on the standard track. This is fairly limiting, as it excludes stuff like TrustedTypes (which are allowlisted currently) and Navigator.deviceMemory, which are commonly used APIs. Instead, we should only care about whether something is on the standard track. TBD is whether we want to include stuff that is both experimental and standard track or only non-experimental.

Metadata

Metadata

Assignees

Labels

P1A high priority bug; for example, a single project is unusable or has many test failuresarea-api-missingtype-enhancementA request for a change that isn't a bug

Type

No type

Projects

Status

Done

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions