Skip to content
This repository has been archived by the owner on Jul 21, 2021. It is now read-only.

Considering dropping Opera from Firefox Platform Status #605

Open
takenspc opened this issue Apr 29, 2020 · 4 comments
Open

Considering dropping Opera from Firefox Platform Status #605

takenspc opened this issue Apr 29, 2020 · 4 comments

Comments

@takenspc
Copy link
Contributor

While I respect great standardization and implementation works from Opera, it is hard to track Opera's platform status:

  • there is no official platform status (while Edge continues to maintain its platform status)
  • though Firefox Platform Status fills in data from Can I use..., not every feature has Can I use... entry

As a result, Opera's position at Firefox Platform Status looks very inconsistent. At Firefox Platform Status, Opera looks like not to support Asynchronous Clipboard API, Web Animations API and many other features.

In general speaking, Opera's platform status is considered same as Chrome's one. There are rarely occasions when it is necessary to make a distinction between them.

Thus, I propose that dropping Opera from Firefox Platform Status until Opera starts to maintain its platform status.

@digitarald
Copy link
Contributor

Agreed, they don't seem to actively invest in the platform as much anymore and/or doing outreach to devs.

@digitarald
Copy link
Contributor

@chrisdavidmills what's the compat data view on opera?

@chrisdavidmills
Copy link
Contributor

@digitarald we have compat data for Opera and Opera mobile on our compat data repo, but generally it is just worked out from the chrome version number/status. I don't think we'd miss a lot from removing it; we could perhaps add something to indicate that Chrome support also implies support for the other chromium-based browsers, although this is fairly obvious to any web dev.

@digitarald
Copy link
Contributor

we could perhaps add something to indicate that Chrome support also implies support for the other chromium-based browsers, although this is fairly obvious to any web dev.

Right, same for Samsung, Edge Chromium, Brace, etc. Keeping track of them all or even picking one isn't great. Maybe changing the icon to a more general Chromium icon can also clarify that.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants