@@ -382,8 +382,8 @@ Requirements for Responsible Implementation of CSS</h2>
382382 the CSSWG recommends the following best practices for the implementation of
383383 <a>unstable</a> features and <a>proprietary extensions</a> to CSS:
384384
385- <ol >
386- <li >
385+ <h4 id="unstable" >
386+ Experimentation and Unstable Features</h4 >
387387
388388 Issue: Rewritten per gregwhitworth's feedback.
389389
@@ -419,7 +419,8 @@ Requirements for Responsible Implementation of CSS</h2>
419419 Note: Vendors should consult the WG explicitly and not make assumptions on this point,
420420 as a pre-CR spec that hasn't changed in awhile is usually more out-of-date than stable.
421421
422- <li>
422+ <h4 id="de-facto">
423+ Market Pressure and De Facto Standards</h4>
423424
424425 Issue: Added "should not" against encumbered features, per dbaron's request.
425426
@@ -470,7 +471,8 @@ Requirements for Responsible Implementation of CSS</h2>
470471 that cannot be freely implemented by their competitors
471472 (due to platform dependency, licensing restrictions, etc.).</ins>
472473
473- <li>
474+ <h4 id="proprietary">
475+ Proprietary and Non-standardized Features</h4>
474476
475477 Issue: Rewritten as open vs. closed systems instead of Web vs. non-Web, per szilles' request.
476478
@@ -501,7 +503,6 @@ Requirements for Responsible Implementation of CSS</h2>
501503 Even if a feature is intended to eventually be used in the Web,
502504 if it hasn't yet been standardized
503505 it should still not be exposed to the Web.
504- </ol>
505506
506507
507508<h3 id="testing">Implementations of CR-level Features</h3>
0 commit comments