You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 2, 2023. It is now read-only.
Creating an explicit web standard to lock out browsers you didn't certify is going to put Google on the wrong end of a losing anti trust lawsuit, and make the lives of all the engineers involved miserable in the process.
Do yourself a favor and abandon this proposal, before you have to spend the next few years of your life going through depositions and subpoenas.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Creating an explicit web standard to lock out browsers you didn't certify is going to put Google on the wrong end of a losing anti trust lawsuit, and make the lives of all the engineers involved miserable in the process.
Do yourself a favor and abandon this proposal, before you have to spend the next few years of your life going through depositions and subpoenas.
The text was updated successfully, but these errors were encountered: