@@ -475,22 +475,22 @@ Market Pressure and De Facto Standards</h4>
475475 the implementations are sufficiently similar
476476 to be used in production websites for a substantial number of use cases.
477477
478+ <p class="note"> Note that the CSSWG must still be consulted to ensure coordination across vendors
479+ and to ensure sanity review by the CSS experts from each vendor.
480+ Note also that <a>rough interoperability</a> still usually means
481+ painful lack of interop in edge (or not-so-edge) cases,
482+ particularly because details have not been ironed out through the standards review process.
483+
478484 <details class=why>
479485 <summary> Why?</summary>
480486 If a feature is sufficiently popular that three or more browsers have implemented it before it's finished standardization,
481487 this clause allows releasing the pressure to ship.
482488 Also, if a feature has already escaped into the wild and sites have started depending on it,
483- pretending it's still " experimental" doesn't help anyone.
489+ pretending it's still “ experimental” doesn't help anyone.
484490 Allowing others to ship unprefixed recognizes that the feature is now de facto standardized
485491 and encourages authors to write cross-platform code.
486492 </details>
487493
488- <p class="note"> Note that the CSSWG must still be consulted to ensure coordination across vendors
489- and to ensure sanity review by the CSS experts from each vendor.
490- Note also that <a>rough interoperability</a> still usually means
491- painful lack of interop in edge (or not-so-edge) cases,
492- particularly because details have not been ironed out through the standards review process.
493-
494494<h5 id="unstable-syntax" class="no-toc">
495495Vendor-prefixing Unstable Features</h5>
496496
0 commit comments