| ▲ | troupo 30 minutes ago | |
> As long as this is the current state of things with WebKit Firefox also rejects the Chrome-only non-standards > ultimately gets veto power over any standard the rest of the industry does agree on Where "rest of industry" is invariably "we build from Chromium source code with very little changes". Apple very rarely vetoes standards that non-Chromium browsers (aka Firefox) also agrees on. Edit: > and random HTML and CSS features will sit functionally unusable HTML and CSS features Apple is usually very much behind, and ships them very much on time with everyone else. They are often held back by Apple's own inane "release yearly" schedule. See interop 2025 vs 2026: https://wpt.fyi/interop-2025?stable vs https://wpt.fyi/interop-2026?stable and then click to "experimental" | ||