@@ -493,8 +493,8 @@ Requirements for Responsible Implementation of CSS</h2>
493
493
<p> When exposing such an <a>unstable</a> feature to the Web in a production release,
494
494
implementations should support both prefixed and unprefixed syntaxes
495
495
for the feature.
496
- <ins> Once the feature has stabilized and the implementation is updated to match interoperable behavior,
497
- support for the prefixed syntax should be removed.</ins>
496
+ Once the feature has stabilized and the implementation is updated to match interoperable behavior,
497
+ support for the prefixed syntax should be removed.
498
498
499
499
<details class=why>
500
500
<summary> Why?</summary>
@@ -504,12 +504,13 @@ Requirements for Responsible Implementation of CSS</h2>
504
504
as they get ironed out through the standards/bugfixing process.
505
505
</details>
506
506
507
- <p> Vendors should <ins> make it possible for other implementors
507
+ In order to preserve the open nature of CSS as a technology,
508
+ vendors should make it possible for other implementors
508
509
to freely implement any features that they do ship.
509
- To this end, they should</ins> provide spec-editing and testing resources
510
+ To this end, they should provide spec-editing and testing resources
510
511
to complete standardization of such features,
511
- <ins> and avoid other obstacles (e.g., platform dependency, licensing restrictions)
512
- to their competitors shipping the feature.</ins>
512
+ and avoid other obstacles (e.g., platform dependency, licensing restrictions)
513
+ to their competitors shipping the feature.
513
514
514
515
515
516
<h3 id="testing">Implementations of CR-level Features</h3>
0 commit comments