&gt; It seems they agree the existing state of affairs isn&#x27;t acceptable, but don&#x27;t agree about how to proceed.<p>They completely agree how to proceed, Firefox and Chrome both moved to using feature flags instead of vendor prefixes a while back, but there are so many -webkit- prefixed &quot;advanced&quot; properties in the wild, and developers only testing their site in Chrome (which hasn&#x27;t removed the old prefixed properties for compatibility reasons) that Mozilla felt compelled to add support for these. Incidentally, they&#x27;re following Opera[0] and Microsoft[1] in doing so.<p>&gt; while Apple announces dropping the same prefixes<p>Apple didn&#x27;t announce dropping support for <i>existing</i> prefixed properties (at best they noted that they may remove some over time depending on compatibility needs), only that new features will be gated instead of prefixed going forwards.<p>&gt; it also means they&#x27;ll have this prefix code as an artifact for some time while it becomes increasingly irrelevant.<p>Prefixed properties are just specific names, the vendor prefix is incidental, Mozilla implemented and enabled a bunch of properties named -webkit-{something} instead of {something}.<p>[0] <a href="http:&#x2F;&#x2F;www.sitepoint.com&#x2F;opera-css3-webkit-prefix&#x2F;" rel="nofollow">http:&#x2F;&#x2F;www.sitepoint.com&#x2F;opera-css3-webkit-prefix&#x2F;</a><p>[1] <a href="https:&#x2F;&#x2F;msdn.microsoft.com&#x2F;en-us&#x2F;library&#x2F;mt270097%28v=vs.85%29.aspx" rel="nofollow">https:&#x2F;&#x2F;msdn.microsoft.com&#x2F;en-us&#x2F;library&#x2F;mt270097%28v=vs.85%...</a>