3 ms·

Those non-standards are aggressively pushed by Chrome, and shipped by default by Chrome first. Calling it Chromium makes it sound like they somehow originate i

• jacooper 4y ago
  TIL, I though chromium always was ahead of chrome, so all changes end up in chromium first, therefore also other chromium based browsers get the patch/nonstandard behavior.
  • dmitriid 4y ago
    Chromium might get those features purely due to Chrome's release cadence. So the code may be enabled the code base without flags before it ships in Chrome (Chrome releases are monthly). Most of Chromium-based browsers will probably lag on those features because they either don't want them, or have their own release cadence, or are running an older version etc. And it's only Chrome that pretends that their non-standard features are standard, and employs a large network of propaganda from web.dev[1] to dev rels[2] to advertise them as standards. [1] Example WebTransport https://web.dev/webtransport/ https://web.dev/webtransport/, multiple non-standard hardware APIs https://web.dev/devices-introduction/ https://web.dev/devices-introduction/ [2] I sadly lost the link to tweet from either Justing Fagnani or Alex Russel where they called the decision to ship Constructible Stylesheets "bravery to move the platform forward". Context: trivial deadlock issues in the spec, both Mozilla and Safari were dead set against it until issues could be fixed, Google-led lit-html wanted the functionality, so Chrome just shipped it.